From: Laurenz Albe <laurenz.albe@cybertec.at>
To: Tom Lane <tgl@sss.pgh.pa.us>
To: Andrew Dunstan <andrew.dunstan@2ndquadrant.com>
Cc: Andres Freund <andres@anarazel.de>
Cc: pgsql-hackers@postgresql.org
Subject: Re: language cleanups in code and docs
Date: Wed, 17 Jun 2020 12:06:18 +0200
Message-ID: <ca7f852cf4c27eaf26da7a76b5d427e4d333a7c4.camel@cybertec.at> (raw)
In-Reply-To: <1406831.1592351744@sss.pgh.pa.us>
References: <20200615182235.x7lch5n6kcjq4aue@alap3.anarazel.de>
<4601de0f-fc81-de87-7173-75fee5497f85@2ndQuadrant.com>
<1406831.1592351744@sss.pgh.pa.us>
On Tue, 2020-06-16 at 19:55 -0400, Tom Lane wrote:
> Andrew Dunstan <andrew.dunstan@2ndquadrant.com> writes:
> > On 6/15/20 2:22 PM, Andres Freund wrote:
> > > 2) 'master' as a reference to the branch. Personally I be in favor of
> > > changing the branch name, but it seems like it'd be better done as a
> > > somewhat separate discussion to me, as it affects development
> > > practices to some degree.
> > I'm OK with this, but I would need plenty of notice to get the buildfarm
> > adjusted.
>
> "master" is the default branch name established by git, is it not? Not
> something we picked. I don't feel like we need to be out front of the
> rest of the world in changing that. It'd be a cheaper change than some of
> the other proposals in this thread, no doubt, but it would still create
> confusion for new hackers who are used to the standard git convention.
I have the feeling that all this is going somewhat too far.
I feel fine with removing the term "slave", even though I have no qualms
about enslaving machines.
But the term "master" is not restricted to slavery. It can just as well
imply expert knowledge (think academic degree), and it can denote someone
with the authority to command (there is nothing wrong with "servant", right?
Or do we have to abolish the term "server" too?).
I appreciate that other people's sensitivities might be different, and I
don't want to start a fight over it. But renaming things makes the code
history harder to read, so it should be used with moderation.
Yours,
Laurenz Albe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: laurenz.albe@cybertec.at, tgl@sss.pgh.pa.us, andrew.dunstan@2ndquadrant.com, andres@anarazel.de
Subject: Re: language cleanups in code and docs
In-Reply-To: <ca7f852cf4c27eaf26da7a76b5d427e4d333a7c4.camel@cybertec.at>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox