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

Dominik Psenner dpsenner at gmail.com
Thu Mar 24 10:19:20 CDT 2011


> -----Original Message-----
> From: mercurial-devel-bounces at selenic.com [mailto:mercurial-devel-
> bounces at selenic.com] On Behalf Of timeless
> Sent: Thursday, March 24, 2011 3:50 PM
> To: Martin Geisler
> Cc: Mercurial Developers
> Subject: Re: Enable "hg push --new-branch" by default in hgrc
> 
> On Thu, Mar 24, 2011 at 4:34 PM, Martin Geisler <mg at aragost.com> wrote:
> > I would counter that you don't have that many options: if you've created
> > the branch, then you'll want to push it sooner or later since we don't
> > really have a good way of abandoning a branch (except dead heads..).
> 
> I don't ever want to push my branches.
> 
> mxr is developed on default (http://hg.mozilla.org/webtools/mxr)
> 
> each deployment is versioned on a named branch (meego, konigsberg,
> landfill, maemo, ....).
> 
> the changes from a named branch are versioned because they're changes,
> and can be backed up too, but they never belong upstream.

This is a different usecase than we have. Long scale development is mostly
done in default. We branch things that are either:

* bugs / tasks
* features that involve a lot/large changes

But all branches are sooner or later merged into default. That could be
several commits for a few hours if it is a bugfix and several days or weeks
for a feature that may be merged into default more than only once.

> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at selenic.com
> http://selenic.com/mailman/listinfo/mercurial-devel



More information about the Mercurial-devel mailing list