Re: Re* [PATCH 8/9] fast-export: respect the possibly-overridden default branch name

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Jun 23, 2020, 21:11 UTC
Message-ID: <nycvar.QRO.7.76.6.2006232309190.54@tvgsbejvaqbjf.bet>
In-Reply-To: <xmqqtuz9tq30.fsf@gitster.c.googlers.com>

Hi Junio,

On Wed, 17 Jun 2020, Junio C Hamano wrote:

Show 11 quoted lines

> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
> > Yes, the trouble with `maint` did cross my mind, but I try not to
> > "overfit" to git/git. :-)
>
> I do not think it is overfitting; if the solution cannot even
> support the originating project well, there is something wrong.
>
> Most likely, I'd be tempted to rename it myself away from any name
> that is too similar to 'maint'; perhaps to 'stable' (or 'devo', h/t
> tla ;-).

You could also use `next` instead of `master`, which would make intuitive sense because the commits that make it into that branch are slated to be part of the next major Git version.

And a relatively obvious name for the current `next` might be `cooking`.

I refrained from proposing this earlier, thinking that this would be too disruptive, but since `pu` was renamed to `seen`...

:-)

Ciao, Dscho