Re: unexpected git-merge result
- From
- Dale Rowley <ddrowley3@juno.com>
- Date
- Feb 20, 2010, 03:45 UTC
- Message-ID
- <loom.20100220T031401-572@post.gmane.org>
- In-Reply-To
- <7vaav4amjj.fsf@alter.siamese.dyndns.org>
Junio C Hamano <gitster <at> pobox.com> writes:
> It can happen if F is a cherry-pick of D and G is a revert of F, for > example. >
You're exactly right. I overlooked the cherry-pick, which clears things up a bit. But the basic problem remains:
A----D---E---H \ / B--D'----G
G only removed a few of the lines that were brought over in the cherry-pick (D'), so it was surprising when they re-appeared in H. Intuitively, one would at least expect a conflict in H since D'+G is asserting that these lines should not exist, whereas D (on the other branch) is asserting that they should. I can see how it would be difficult to make git-merge account for this though, so maybe this is just a subtle gotcha when merging branches? Is there an easy way to avoid this gotcha?
Dale