David Jeske wrote: > reorder: Picture that a list of commits on this branch opens in an editor. You > are free to rearrange the lines in any order you want, but you have to keep all > the lines. When you are done reordering the lines, the tool creates a new topic > branch and applies the changes (probably with cherrypick) to the new topic > branch. If there are no conflicts, you're done. > > merge: Picture now that in your editor you can create groupings of those > individual commits that should make up separate topic-branches. The operation > can still be performed automatically, and at the end, it can compose those > topic branches into a single branch just like your original. At this point, you > can "isolate" any one of those topic branches and test/push that topic branch. git rebase --interactive? Any patch management interface (StGIT, Guilt)? -- Jakub Narebski Warsaw, Poland ShadeHawk on #git -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
