[issue2028] hg push doesn't always warn when pushing new named branches

Benoit Boissinot bugs at mercurial.selenic.com
Sat Feb 6 12:18:52 CST 2010


New submission from Benoit Boissinot <bboissin at gmail.com>:

hg push sometimes doesn't require --force when it should when using --rev.

hg init t1
cd t1
echo a > a
cd ..
hg clone t1 t2
cd t2
echo b > b
hg branch foo
hg ci -Am m
hg up default
echo c > c
hg ci -Am m
hg merge foo
hg ci -m m
echo cc > c
hg ci -Am m
hg out
hg push # should require --force
hg out -r 3
hg push -r 3 # shouldn't work without --force, since it adds a new branch

----------
messages: 11627
nosy: tonfa
priority: bug
status: unread
title: hg push doesn't always warn when pushing new named branches
topic: named branches, surprise

____________________________________________________
Mercurial issue tracker <bugs at mercurial.selenic.com>
<http://mercurial.selenic.com/bts/issue2028>
____________________________________________________


More information about the Mercurial-devel mailing list