git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Whinis <Whinis@whinis.com>
To: peff@peff.net
Cc: bturner@atlassian.com, git@vger.kernel.org, james@jramsay.com.au,
	me@ttaylorr.com, msuchanek@suse.de
Subject: Re: Consensus on a new default branch name
Date: Thu, 2 Jul 2020 08:21:35 -0400	[thread overview]
Message-ID: <16f1c63a-8b30-e95e-50d1-c5baa9a72fa4@whinis.com> (raw)
In-Reply-To: <20200701215744.GA952178@coredump.intra.peff.net>

Peff,

With all respect I have yet to see any evidence actually presented 
against master either. The original list makes the claim its offensive 
and everyone I have asked on other forums just says its obvious its 
offensive but cannot say how it is without resorting to `Do you not find 
enslaving humans offensive`. About all we have is twitter where you can 
easily find people saying its time to go and that changing it makes them 
feel worse as they had no problem with it and yet its being forced 
through in their name. L makes a case with research that the initial 
claim was also not made in good faith at 
https://lore.kernel.org/git/20200621195023.3881634-1-lkcl@lkcl.net/ . 
The link is also more on the master/slave depart but many of the points 
researched cover this one as well.

I like that you want to err on the side of empathy but based on how most 
of these changes have been forced through their communities I do not 
think the ones arguing for this would do the same for you. As can 
partially be seen with the claim that there is no amount of work that 
can justify continuing to use master or a host of other terms.

My personal feeling is it should not change as while many on this list 
certainly are speaking in good faith and want to help the momentum 
behind the change very much is not. While I know its not part of this 
list check out the gitlab issue where they finally opened it back up for 
discussion at https://gitlab.com/gitlab-org/gitlab/-/issues/221164 and 
it adds onto those that seem to argue for attack any who argue against. 
If a change is going to be made that will affect million of developers 
and possibly break thousands to millions of applications  I would say 
that you need a mountain of proof and not what has been seen so far.

If I may ask what is the intended result of the change if it cannot be 
measured?

-Whinis


  reply	other threads:[~2020-07-02 12:19 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
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 [this message]
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=16f1c63a-8b30-e95e-50d1-c5baa9a72fa4@whinis.com \
    --to=whinis@whinis.com \
    --cc=bturner@atlassian.com \
    --cc=git@vger.kernel.org \
    --cc=james@jramsay.com.au \
    --cc=me@ttaylorr.com \
    --cc=msuchanek@suse.de \
    --cc=peff@peff.net \
    /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).