[issue911] "branch default not found"...

[Antoine]

New submission from Antoine <pitrou at free.fr>:

Hi,

I find that Mercurial could be smarter with its "default" branch...
For example if you create a repository ("hg init t"), typing "hg up" in this
repository gives "branch default not found" : indeed, since no changeset has
been recorded yet, the branch does not exist in the repository...

More annoying is when you have a repository created before 0.9.5 (or is it
0.9.4?). In this case you can have one several named branches but none of them
named "default". Then, once again, "hg up" instead of staying in the branch of
the tip (or of the wc), complains about "branch default not found".

Finally, the naming "default" is not satisfying for all uses. For example, I
clone and follow SVN branches using Mercurial. Thus there is most of the time a
named branch "trunk" and other named branches depending on which SVN branches I
want to follow. I definitely do NOT want a branch named "default" to interfere
with that setup (and "trunk" is not more "default" than the others ;-)).

So, please, Mercurial may create a "default" branch if the user never specified
a specific branch when creating the first changeset in the repo, but it would be
best if that "default" branch was not imposed on the user when he has other
ideas about how he wants to organize his work.

(by the way, this is with stable version 0.9.5... perhaps it is fixed already?)

----------
messages: 4814
nosy: pitrou
priority: bug
status: unread
title: "branch default not found"...

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