I'd like to clarify a strange behaviour that I've encountered recently with 
I've merged a feature branch "X" into a release branch, let's call it 
"release". This branch introduced a very difficult to debug issue and it 
contained a lot of commits so I've decided to revert the entire merge 
itself with 

git revert -m 1 <sha_of_merge>

(see: http://git-scm.com/blog/2010/03/02/undoing-merges.html)

This was fine but later on I've merged "release" into "master". And I've 
discovered that this merge actually merged into master also the changes 
from "X", like if it has never been reverted from "release".
Is this expected behaviour or I must be missing something else?



You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to git-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to