Thomas Glanzmann wrote: >Hello Andreas, > > > >>Something like this might do the trick, depending on how linear your >>ancestry graph is: >> >> > > > >>$ cd blastwave >>$ first=$(git rev-list HEAD | tail -n 1) >>$ git format-patch -k --stdout $first..HEAD > ../blw.mbox >>$ cd ../blastwave.old >>$ git am -k -3 ../blw.mbox >> >> > >My graph is very linear. However. I have binaries checked into my tree. >I am not sure if format-patch can handle this. > > I wrote a program called "graft-ripple", that takes a commit, and rewrites the current branch's history to reflect as if it started at that commit. It doesn't ever actually work with diffs or anything, it just reads commits and trees and recreates them. It's in the list archives, but I appear to have deleted it when I was cleaning up my archives. http://www.gelato.unsw.edu.au/archives/git/0511/12965.html Hope this helps! -- Ryan Anderson sometimes Pug Majere - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
This archive was generated by hypermail 2.1.8 : 2006-02-20 21:58:59 EST