On 12 January 2011 22:13, Claus Reinke <claus.rei...@talk21.com> wrote: >> You can emulate darcs's patch re-ordering in git if you put each >> independent sequence of patches on a separate branch. Then you can >> re-merge the branches in whatever order you want. This is a fairly >> common git workflow. > > What happens after the merges? Does one maintain the branches > somehow, or does one lose the (in-)dependency information?
If you are interested in this approach. you can check out Iolaus, which is David Roundy's attempt at getting Darcs-style revision control in Git: https://github.com/droundy/iolaus. I think that it relies on you, the user, to accurately specify which patches a new one of your own depends on, which is a bit of a limitation. Cheers, Max _______________________________________________ Glasgow-haskell-users mailing list Glasgow-haskell-users@haskell.org http://www.haskell.org/mailman/listinfo/glasgow-haskell-users
