https://bz.mercurial-scm.org/show_bug.cgi?id=6498
Bug ID: 6498 Summary: [evolve] user/username confusion Product: Mercurial Version: 5.7.1 Hardware: PC OS: All Status: UNCONFIRMED Severity: bug Priority: wish Component: evolution Assignee: bugzi...@mercurial-scm.org Reporter: asheme...@gmail.com CC: mercurial-devel@mercurial-scm.org, pierre-yves.da...@ens-lyon.org Python Version: --- (This seems slightly improved in 5.7.x in that it doesn't allow you to commit without supplying a username thereby limiting shooting yourself in the foot as much, in earlier versions this was less an issue since it seems to have defaulted to your login on Linux/Unix systems.) When using many of evolve's commands with --user "Name <em...@domain.tld>" while $HOME/.hgrc has no username set, the command will abort with an "abort: no username supplied", e.g.: $ hg metaedit --user "Name <em...@domain.tld>" transaction abort! rollback completed abort: no username supplied (use 'hg config --edit' to set your username) Given how user/username are understood by many people as being synonyms, this can be quite confusing. I also initially got stumped a bit why I couldn't make this work. That is, until I spoke with marmoute and mharbison on IRC. This might be sort of related to bug 3169 and bug 3898. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ Mercurial-devel mailing list Mercurial-devel@mercurial-scm.org https://www.mercurial-scm.org/mailman/listinfo/mercurial-devel