On 7/9/08, Jan Rychter <jan@xxxxxxxxxxx> wrote: > The way this would work is I would have one or two long-term development > branches, and each of those would depend on a list of "live branches", > managed by a tool similar to StGIT. I should be able to commit to either > the main development branch, or to one of the "live branches", in which > case I should be able to easily "resync" the main development branch (do > a merge or a rebase, but I would prefer the tool to first remove old > merge commits, so as not to clutter history). Hmm, git rebase already removes old merge commits. In my own workflow, I tend to do repeated merges of the "live branch" into my feature branches during development, then do a rebase occasionally to clean up the patch set, especially right before merging it into master. This seems pretty painless to me. What specific problem are you having that prevents this from working? Have fun, Avery -- 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
