From: DJ Delorie <dj@redhat.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: carlos@redhat.com, libc-alpha@sourceware.org, schwab@suse.de,
joseph@codesourcery.com, eggert@cs.ucla.edu, fweimer@redhat.com,
ryan.arnold@gmail.com, jakub@redhat.com,
maxim.kuvyrkov@linaro.org
Subject: Re: Rename "master" branch to "main" for glibc 2.35 release.
Date: Mon, 31 Jan 2022 13:28:20 -0500 [thread overview]
Message-ID: <xnbkzryd2z.fsf@greed.delorie.com> (raw)
In-Reply-To: <e3bc84a9-7516-6653-7ce4-82e5952db935@linaro.org> (message from Adhemerval Zanella on Mon, 31 Jan 2022 15:09:19 -0300)
Adhemerval Zanella <adhemerval.zanella@linaro.org> writes:
> I must say that I am failing to see any technical advantage or improvement
> of doing this change.
There isn't any. This is a response to a vocal group in the USA that
feels that words can't change, and "master/slave" will always mean
historic slavery and nothing else, and since their way is the only way,
the rest of the world has to change intead.
Obviously, I'm opposed to such things ;-)
The only example of "doing it right" I've seen so far, is that Fedora
changed their master branch to "rawhide" which actually makes a lot of
sense, since that's where that branch is used.
Note: I'm not opposed to renaming the master branch *per se*. After
all, it's just a word. I'm opposed to doing it *for those reasons* and
in a way which inconveniences our users. Do it right, do it better, or
don't do it at all.
next prev parent reply other threads:[~2022-01-31 18:28 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 22:32 Carlos O'Donell
2022-01-29 22:45 ` Phil Blundell
2022-01-29 23:33 ` DJ Delorie
2022-01-30 1:35 ` Mike Frysinger
2022-01-30 2:10 ` DJ Delorie
2022-01-30 3:45 ` Mike Frysinger
2022-01-30 2:35 ` Paul Eggert
2022-01-30 5:41 ` Siddhesh Poyarekar
2022-01-31 12:46 ` Florian Weimer
2022-01-31 13:41 ` Andreas Schwab
2022-01-31 14:55 ` Carlos O'Donell
2022-02-01 0:59 ` Dmitry V. Levin
2022-02-01 3:05 ` Carlos O'Donell
2022-01-31 12:50 ` Tulio Magno Quites Machado Filho
2022-01-31 16:19 ` Joseph Myers
2022-01-31 17:59 ` Dan Raymond
2022-01-31 18:04 ` Dan Raymond
2022-01-31 22:49 ` Carlos O'Donell
2022-01-31 23:04 ` Joseph Myers
2022-02-01 3:02 ` Carlos O'Donell
2022-01-31 18:09 ` Adhemerval Zanella
2022-01-31 18:14 ` H.J. Lu
2022-01-31 18:21 ` Adhemerval Zanella
2022-01-31 18:28 ` DJ Delorie [this message]
2022-02-01 3:08 ` Siddhesh Poyarekar
2022-02-01 3:44 ` DJ Delorie
2022-02-01 5:05 ` Siddhesh Poyarekar
2022-02-01 7:25 ` Carlos O'Donell
2022-01-31 20:15 ` Siddhesh Poyarekar
2022-01-31 21:24 ` Adhemerval Zanella
2022-02-01 2:51 ` Siddhesh Poyarekar
2022-02-01 9:49 ` Florian Weimer
2022-02-01 10:26 ` Siddhesh Poyarekar
2022-02-03 5:57 ` Carlos O'Donell
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=xnbkzryd2z.fsf@greed.delorie.com \
--to=dj@redhat.com \
--cc=adhemerval.zanella@linaro.org \
--cc=carlos@redhat.com \
--cc=eggert@cs.ucla.edu \
--cc=fweimer@redhat.com \
--cc=jakub@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=maxim.kuvyrkov@linaro.org \
--cc=ryan.arnold@gmail.com \
--cc=schwab@suse.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).