[Bug 4207] New: warn early on rebase when username is not set
mercurial-bugs at selenic.com
mercurial-bugs at selenic.com
Wed Mar 26 09:25:17 CDT 2014
http://bz.selenic.com/show_bug.cgi?id=4207
Priority: normal
Bug ID: 4207
CC: mercurial-devel at selenic.com
Assignee: bugzilla at selenic.com
Summary: warn early on rebase when username is not set
Severity: bug
Classification: Unclassified
OS: Windows
Reporter: techtonik at gmail.com
Hardware: PC
Status: UNCONFIRMED
Version: 2.9
Component: rebase
Product: Mercurial
It is no good to drop user into the middle of rebase transaction due to missing
username. Is it possible to warn user before initiating rebase about missing
username?
The story in command line language:
>hg phase -d -r branch(pixels)
cannot move 2 changesets to a higher phase, use --force
no phases changed
>hg phase -d -r branch(pixels) -f
>hg rebase -b . -d tip
abort: no username supplied (see "hg help config")
>hg log -r branch(pixels)
...
>hg strip -r 187
abort: rebase in progress
(use 'hg rebase --continue' or 'hg rebase --abort')
>hg rebase --continue
abort: no username supplied (see "hg help config")
>hg --version
Mercurial Distributed SCM (version 2.9)
(see http://mercurial.selenic.com for more information)
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the Mercurial-devel
mailing list