Enable "hg push --new-branch" by default in hgrc

[Matt Mackall]

On Fri, 2011-03-25 at 08:56 +0100, Dominik Psenner wrote:
> I've got another usecase for "issue" named branches. A bugtracking tool
> could easily gather changesets related to the issue identified by IssueId
> and link to those changes by invoking something like:
> 
> $ hg log -b IssueId

You don't need a branch to do that:

$ hg log -k issue2561
changeset:   13693:adf3c4401c5d
branch:      stable
user:        Miloš Hadžić <milos.hadzic at gmail.com>
date:        Thu Mar 17 22:55:02 2011 +0100
summary:     push/outgoing: print remote target path even if there's an
error (issue2561)

> Would you please tell me more about possible scalability problems and
> (computational) borders that can be encountered?

Realistically, you're going to be the one telling us, because you'll be
the only user with thousands of named branches.

-- 
Mathematics is the supreme nostalgia of our time.