On Sep 24, 10:44 pm, Konstantin Khomoutov <khomou...@gmail.com> wrote:
> [...]
> If, on the other hand, you're OK with history rewriting (for instance,
> you don't publish your branches), you supposedly can do this:
> 1) Commit the change on one branch;
> 2) Do rebasing of this branch so that the committed change appears
> after some specific commit in the branch history (supposedly it should
> be some commit earlier than the common ancestor of all the branches
> interested in the change you just made).
> 3) Rebase the rest of the branches on top of that new commit
> containing the change.
> I suppose this approach should be a bit less cumbersome than git-
> filter-branch.

Thank you Konstantin. Lately, I realize that this is mentioned in the
git-rebase manual as well.

You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To post to this group, send email to git-users@googlegroups.com
To unsubscribe from this group, send email to 
For more options, visit this group at 

Reply via email to