From: Brandon Casey <drafnel@gmail.com>
To: "Theodore Y. Ts'o" <tytso@mit.edu>
Cc: 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: Wed, 18 Nov 2020 17:02:59 -0800
Message-ID: <CA+sFfMfWrSMKAogg-5dsaO_beXUV-JCBLBPeLZ5g_0jGqsom8Q@mail.gmail.com> (raw)
In-Reply-To: <20201115034649.GC3985404@mit.edu>
On Sat, Nov 14, 2020 at 8:23 PM Theodore Y. Ts'o <tytso@mit.edu> 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"?
For what purpose? What problem are we trying to solve?
Is the word "master" now going to become a taboo word that we're all
afraid to say?
Isn't this all a little silly? What's wrong with the term "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.
-Brandon
next prev parent reply other threads:[~2020-11-19 1:05 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 0:04 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 [this message]
2020-11-19 4:16 ` Peter Hadlaw
2020-11-19 13:37 ` Konstantin Ryabitsev
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CA+sFfMfWrSMKAogg-5dsaO_beXUV-JCBLBPeLZ5g_0jGqsom8Q@mail.gmail.com \
--to=drafnel@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=Lukasz.Niemier@kobil.com \
--cc=don@goodman-wilson.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
git@vger.kernel.org list mirror (unofficial, one of many)
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://public-inbox.org/git
git clone --mirror http://ou63pmih66umazou.onion/git
git clone --mirror http://czquwvybam4bgbro.onion/git
git clone --mirror http://hjrcffqmbrq6wope.onion/git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V1 git git/ https://public-inbox.org/git \
git@vger.kernel.org
public-inbox-index git
Example config snippet for mirrors.
Newsgroups are available over NNTP:
nntp://news.public-inbox.org/inbox.comp.version-control.git
nntp://ou63pmih66umazou.onion/inbox.comp.version-control.git
nntp://czquwvybam4bgbro.onion/inbox.comp.version-control.git
nntp://hjrcffqmbrq6wope.onion/inbox.comp.version-control.git
nntp://news.gmane.io/gmane.comp.version-control.git
note: .onion URLs require Tor: https://www.torproject.org/
code repositories for the project(s) associated with this inbox:
https://80x24.org/mirrors/git.git
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git