Conflict resolution merge commit seems incomplete
Posted
by
kayaker243
on Stack Overflow
See other posts from Stack Overflow
or by kayaker243
Published on 2012-10-05T21:02:17Z
Indexed on
2012/10/05
21:37 UTC
Read the original article
Hit count: 247
There was a feature branch with conflicts. These were resolved and the resolution committed.
Unfortunately, I botched the merge and a couple previously-released features regressed - this is verified by doing a diff between the merge commit sha1 and that of the previous tag.
When I do git show <sha1 for merge commit>
all changes are innocuous.
When I do git log -Sunique_variable_added_for_feature_and_lost_after_botched_merge
, I only see the commit that added unique_variable_...
but not the problematic deletion from the bad merge.
However, when I took the ignominious step of viewing the sha1 for the commit in a gui git client like Tower, I can clearly see the botched lines.
Is there an additional switch used by Tower that I've missed entirely? Why didn't pickaxe pick up the deletion implicit in the merge commit?
© Stack Overflow or respective owner