From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: Oleg <lego_12239@rambler.ru>
Cc: git@vger.kernel.org
Subject: Re: Consensus on a new default branch name
Date: Tue, 16 Jun 2020 13:32:27 -0400 [thread overview]
Message-ID: <20200616173227.inexk4clqilojg36@chatter.i7.local> (raw)
In-Reply-To: <20200616171048.GA18874@legohost>
On Tue, Jun 16, 2020 at 08:11:01PM +0300, Oleg wrote:
> > I think it's clear that this _is_ a politically-driven change. It is
> > not
> > helping the software in any technical way to change the name. The
>
> Yes. You are absolutely right.
>
> > question is whether the more abstract benefits to people are worth the
> > potential costs.
>
> Of course, not. This is obvious.
Oleg, that doesn't make it an invalid discussion point. If Git was
written in German and the lead branch was called "refs/heads/fuhrer"
(German word for "leader"), you'd be on the opposite side of the
barricades arguing that this needs to be changed because it's offensive
to many people whose immediate family members died in WW2.
And someone else would be reasonably pointing out that "fuhrer" doesn't
mean "The Fuhrer" and nobody is even alive since then anymore, and omg,
why is this even a discussion topic -- isn't there something more
important everyone could work on?
Yes, it's a politically motivated change, but it's clearly important to
quite a few people right now and their views should not be disregarded.
-K
next prev parent reply other threads:[~2020-06-16 17:32 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 20:57 Consensus on a new default branch name Taylor Blau
2020-06-15 21:10 ` Santiago Torres Arias
2020-06-15 21:21 ` Taylor Blau
2020-06-16 14:31 ` Jeff King
2020-06-16 14:52 ` Oleg
2020-06-16 16:00 ` Jeff King
2020-06-16 17:11 ` Oleg
2020-06-16 17:32 ` Konstantin Ryabitsev [this message]
2020-06-16 18:54 ` Oleg
2020-06-16 22:18 ` Jeff King
2020-06-16 16:10 ` Konstantin Ryabitsev
2020-06-16 16:13 ` Santiago Torres Arias
2020-06-16 16:48 ` Jeff King
2020-06-16 16:14 ` Jason Pyeron
2020-06-16 16:47 ` Jeff King
2020-06-16 17:44 ` Steve Litt
2020-06-16 19:00 ` Oleg
2020-06-17 18:06 ` Michal Suchánek
2020-07-01 17:31 ` Michal Suchánek
2020-07-01 21:57 ` Jeff King
2020-07-02 12:21 ` Whinis
2020-07-02 21:15 ` Philip Oakley
2020-07-02 21:59 ` Whinis
2020-07-02 22:47 ` Philip Oakley
2020-07-02 23:08 ` Whinis
2020-07-01 22:25 ` Jonathan Nieder
2020-06-15 22:38 ` Elijah Newren
2020-06-16 14:32 ` Jeff King
2020-06-17 20:13 ` Junio C Hamano
2020-06-15 23:24 ` brian m. carlson
2020-06-16 0:50 ` James Ramsay
-- strict thread matches above, loose matches on Subject: below --
2020-06-16 1:58 Nomen Nescio
2020-06-16 2:22 ` Jonathan Nieder
2020-06-16 2:31 ` Taylor Blau
2020-06-16 14:38 ` Jeff King
2020-06-17 0:01 Anonymous Remailer (austria)
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=20200616173227.inexk4clqilojg36@chatter.i7.local \
--to=konstantin@linuxfoundation.org \
--cc=git@vger.kernel.org \
--cc=lego_12239@rambler.ru \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).