[ https://issues.jboss.org/browse/JBIDE-19190?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen edited comment on JBIDE-19190 at 4/27/15 3:59 AM: ---------------------------------------------------------------------- but that is not what https://github.com/jpeterka/jbosstools-vwatch/commits/master shows. so this was moved without retaining git history and attributions ;/ Jiri - I've created https://github.com/jbosstools/jbosstools-versionwatch which *retains* the proper git history as it is in https://github.com/jbdevstudio/jbdevstudio-qa. This was created by running: {code} git filter-branch --prune-empty --subdirectory-filter vwatch -- --all git remote add vwatch https://github.com/jbosstools/jbosstools-versionwatch git push vwatch master jbosstools-4.2.x {code} That means jbosstools-versionwatch now have the proper history *but* missing whatever changes you made in jpeterka. It looks like this can just be cherry-picked over but I think it is best you do it rather than me doing it blindly. Can you make that and submit a PR for it ? was (Author: maxandersen): but that is not what https://github.com/jpeterka/jbosstools-vwatch/commits/master shows. so this was moved without retaining git history and attributions ;/ Jiri - I've created https://github.com/jbosstools/jbosstools-versionwatch which *retains* the proper git history as it is in https://github.com/jbdevstudio/jbdevstudio-qa. This was created by running: {{{ git filter-branch --prune-empty --subdirectory-filter vwatch -- --all git remote add vwatch https://github.com/jbosstools/jbosstools-versionwatch git push vwatch master jbosstools-4.2.x }}} That means jbosstools-versionwatch now have the proper history *but* missing whatever changes you made in jpeterka. It looks like this can just be cherry-picked over but I think it is best you do it rather than me doing it blindly. Can you make that and submit a PR for it ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)