Re: Avoiding 'master' nomenclature

From: Junio C Hamano <gitster@pobox.com>
Date: Aug 10, 2020, 15:45 UTC
Message-ID: <xmqqo8nicxn2.fsf@gitster.c.googlers.com>
In-Reply-To: <nycvar.QRO.7.76.6.2008101349570.50@tvgsbejvaqbjf.bet>

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

> Looks good to me, and apart from the config key (for which I also don't
> have a better suggestion), this looks pretty much how I would have done it
> (but refrained from doing because I really wanted the patch series to be
> part of v2.28.0).

Yes, my fault. What you originally had was "we no longer special case 'master', we special case init.default instead", and after I responded with "why special case anything? everybody is equal ;-)" we ended up marking merges to 'master' as such in the latest release.

The patch you are responding to is much more in line with the way in which we dealt with the special casing of 'master' in the fast-export anonymization in the latest release, and I am reasonably happy with it. Until we need to worry about the "do we need to keep track of which branch is the 'primary' one in this repository automatically?" issue sometime later, that is.

> TBH I expected some discussion along the line "Shouldn't this be an
> opt-in, with the initial default saying 'every branch except `master`'?",
> but that seems not to have taken place.

I do not quite get it. Without any explicit configuration, every branch except 'master' is shown, just like we've done for the past 15 years. You can opt into hiding other names instead of 'master', hiding nothing, or hiding everything.

Thanks.