Quoting skillzero@xxxxxxxxx: > The problem is, by the time I wanted to do the cherry-pick, I had > already committed other stuff to the branch. I tried doing 'git rebase > master branch' when on master and it just applied all the stuff from > master to branch. > > Is there any way to apply a commit to 2 different branches (which have > diverged) in a way that git will remember so that when the 2 branches > merge later, it won't result in duplicate commits? I find that I often > make changes that days or weeks later find out that some other branch > needs that change and by then, there have been lots of commits to both > branches after the commit I want. Johennes Sixt gave a good answer. You need to think before making your commits while you are developing to separate what change belongs to common code base and what change belongs to a specific feature. I was reading gitster's blog (he has several "git tutorial" articles recently) and he talks about how to commit a change to a branch different from what you originally developed it on in today's entry. You may find it instructive, but the procedure is after you think about it and decide what change goes where. -- Nanako Shiraishi http://ivory.ap.teacup.com/nanako3/ -- 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
