[issue1513] push suggests push -f
JillesTjoelker
mercurial-bugs at selenic.com
Fri Feb 13 14:43:27 CST 2009
New submission from JillesTjoelker <jilles at stack.nl>:
When a push is rejected because it would create new heads, it suggests
push -f.
self.ui.warn(_("abort: push creates new remote heads!\n"))
self.ui.status(_("(did you forget to merge?"
" use push -f to force)\n"))
I have noticed that people that use mercurial only occasionally tend to
do hg push -f when they see this message, instead of the
pull/merge/commit sequence that is mentioned in 'hg help push' (or hg
pull --rebase).
That bit of text in 'hg help push' seems to use "the client" in a
somewhat strange way; really, the user (or "you", given that it is used
in some other help files as well) needs to pull/merge/commit to resolve
the issue. (If they want to force or rebase, I think they should find
out about that themselves, it should not be mentioned explicitly.)
----------
messages: 8598
nosy: JillesTjoelker
priority: bug
status: unread
title: push suggests push -f
topic: ui
____________________________________________________
Mercurial issue tracker <mercurial-bugs at selenic.com>
<http://www.selenic.com/mercurial/bts/issue1513>
____________________________________________________
More information about the Mercurial-devel
mailing list