[issue1101] "hg merge" with null revision (000...) sometimes allowed

[Tom Karzes]

New submission from Tom Karzes <Tom.Karzes at magnumsemi.com>:

With version 1.0 of Mercurial, I managed to get it to do a merge with the null
revision (revision 000...).  Usually it rejects this, but if parent 1 is the
null revision and parent 2 is a *named* branch, it slips through.  See the
attached file for detailed information on how to reproduce this.

----------
files: nullmerge.txt
messages: 5962
nosy: tkarzes
priority: bug
status: unread
title: "hg merge" with null revision (000...) sometimes allowed
topic: merge

____________________________________________________
Mercurial issue tracker <mercurial-bugs at selenic.com>
<http://www.selenic.com/mercurial/bts/issue1101>
____________________________________________________
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: nullmerge.txt
Url: http://selenic.com/pipermail/mercurial-devel/attachments/20080425/f879a83c/attachment.txt