Same parent revision twice for a mercurial changeset -
is there canonical explanation why same parent revision listed twice given mercurial changeset resulting merge.
unfortunately, not have chance tell, caused situation in observed case. might situation caused trying perform empty merge operation.
any hints appreciated!
we found out possible way cause kind of situation...
the situation can reproduced tortoisehg selecting local version , "merge local" checking option "discard changes merge target (other) revision".
this not result in calling hg merge
(as 1 assume), hg debugsetparents
. shot ourselves in foot forcing mercurial set both parents same revision.
Comments
Post a Comment