Re: language cleanups in code and docs - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: language cleanups in code and docs
Date
Msg-id 20200617005329.GA14742@alvherre.pgsql
Whole thread Raw
In response to Re: language cleanups in code and docs  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: language cleanups in code and docs  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 2020-Jun-16, 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.

Git itself is discussing this:
https://public-inbox.org/git/41438A0F-50E4-4E58-A3A7-3DAAECB5576B@jramsay.com.au/T/#t
and it seems that "main" is the winning choice.

(Personally) I would leave master to have root, would leave root to have
default, would leave default to have primary, would leave primary to
have base, would leave base to have main, would leave main to have
mainline.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Justin Pryzby
Date:
Subject: Re: Add A Glossary
Next
From: David Zhang
Date:
Subject: Add an option to allow run regression test for individual module onWindows build