From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Brandon Casey <drafnel@gmail.com>
Cc: "Theodore Y. Ts'o" <tytso@mit.edu>,
Lukasz Niemier <Lukasz.Niemier@kobil.com>,
Felipe Contreras <felipe.contreras@gmail.com>,
"brian m. carlson" <sandals@crustytoothpaste.net>,
Git <git@vger.kernel.org>, Junio C Hamano <gitster@pobox.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Don Goodman-Wilson <don@goodman-wilson.com>
Subject: Re: The master branch rename, and avoiding another v1.6.0 git-foo fiasco
Date: Thu, 19 Nov 2020 08:37:05 -0500 [thread overview]
Message-ID: <20201119133705.7q7yghymvvo7zeq4@chatter.i7.local> (raw)
In-Reply-To: <CA+sFfMfWrSMKAogg-5dsaO_beXUV-JCBLBPeLZ5g_0jGqsom8Q@mail.gmail.com>
On Wed, Nov 18, 2020 at 05:02:59PM -0800, Brandon Casey wrote:
> > This *really* is not hard; which is why I am starting to suspect
> > people are really kvetching because their objections are really more
> > about the woke/anti-woke aspect of the "master" -> "main" migration
> > --- and they are using *think* the children^H^H^H^H^H^H^H users as a
> > rhetorical device.
>
> So we're changing the default branch name from "master" to "main"?
To my knowledge, there are no concrete plans to change anything at this
time. All recent work was to remove any special-case treatment of
"master" as the default branch name, so people are free to use any
configuration they like.
> For what purpose? What problem are we trying to solve?
People want to be able to use arbitrary branch names.
> Is the word "master" now going to become a taboo word that we're all
> afraid to say?
No, everyone is welcome to use it if they like. It has perfectly
legitimate usage cases -- for example, some of the staunchest opponents
of this terminology continue to list their "Master of Arts" degree on
LinkedIn.
> Isn't this all a little silly? What's wrong with the term "master"?
It is misleading in the context of git, because it implies that a branch
carrying that name is in some way special compared to other branches
(e.g. like "trunk" in the SVN world). In reality, the "master" branch is
just a branch like all others (and can be missing entirely or have junk
in it), so it really shouldn't be called "master".
> It's a well understood and commonly used term that denotes
> "authority", i.e. the master branch is the authoritative branch.
> People sleep in master bedrooms. Universities have headmasters and
> award master's degrees. Skilled people become master craftsmen and
> give master classes (e.g. master plumber, master diver). Recording
> artists master a track. Skilled chess players become chess masters
> etc.
Exactly, thank you for illustrating my point. In all of the above
situations the word "master" is used to indicate some kind of
distinction. If all you have is a single bedroom, it would be kinda
obnoxious to refer to it as "the master bedroom," eh? :)
-K
next prev parent reply other threads:[~2020-11-19 13:37 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 0:04 The master branch rename, and avoiding another v1.6.0 git-foo fiasco Felipe Contreras
2020-11-13 1:01 ` brian m. carlson
2020-11-13 4:27 ` Felipe Contreras
2020-11-13 5:14 ` Theodore Y. Ts'o
2020-11-13 6:28 ` Felipe Contreras
2020-11-13 14:58 ` Theodore Y. Ts'o
2020-11-13 15:37 ` Felipe Contreras
2020-11-13 16:08 ` Michal Suchánek
2020-11-14 14:19 ` Lukasz Niemier
2020-11-15 3:46 ` Theodore Y. Ts'o
2020-11-15 4:27 ` Felipe Contreras
2020-11-19 1:02 ` Brandon Casey
2020-11-19 4:16 ` Peter Hadlaw
2020-11-19 13:37 ` Konstantin Ryabitsev [this message]
2020-11-19 21:25 ` Junio C Hamano
2020-11-19 23:29 ` Felipe Contreras
2020-11-20 19:14 ` Konstantin Ryabitsev
2020-11-19 21:29 ` Brandon Casey
2020-11-20 0:34 ` Felipe Contreras
2020-11-13 6:09 ` Don Goodman-Wilson
[not found] ` <nbCkLegnP_kb-16UzAuDChE0p68ZtRD_3ZN3o3BJHYBYpUxTWuKjvhCSKT7zRZl_sckHrkyJl2fwePFUBR-HtDcEV0rHuac6Ygg-FrrYsYI=@goodman-wilson.com>
2020-11-13 6:47 ` Felipe Contreras
2020-11-13 13:53 ` Philippe Blain
2020-11-13 15:49 ` Felipe Contreras
2020-11-23 15:39 ` Whinis
2020-11-20 18:38 ` Ismael Luceno
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201119133705.7q7yghymvvo7zeq4@chatter.i7.local \
--to=konstantin@linuxfoundation.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=Lukasz.Niemier@kobil.com \
--cc=don@goodman-wilson.com \
--cc=drafnel@gmail.com \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sandals@crustytoothpaste.net \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).