On Sat, Dec 29, 2012 at 5:47 PM, Lluís Batlle i Rossell <vi...@viric.name> wrote: > Ah sorry, I was only talking about my objections against "git rebase". I don't > know the best way to implement a feature that allows creating 'new history' at > will (not destroying the old). > > All I can imagine sounds like a lot of work. :)
The basic machinery (cherry-pick) is there. The main piece is the interactive rebase, which is really popping the user into $EDITOR to select the order of various operations, and which those are. So there's a) code to select commits, code to format that into a file the user will edit, spawn $EDITOR, then parse the result, then execute it. The execution part requires keeping state and is a bit tricky. The hardest part, I think would be anything like git add -p. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
