list mirror (unofficial, one of many)
 help / color / mirror / Atom feed
From: Philippe Blain <>
To: Felipe Contreras <>
Cc: "D.E. Goodman-Wilson" <>,
	"brian m. carlson" <>,
	Git mailing list <>,
	Junio C Hamano <>,
	Johannes Schindelin <>
Subject: Re: The master branch rename, and avoiding another v1.6.0 git-foo fiasco
Date: Fri, 13 Nov 2020 08:53:35 -0500
Message-ID: <> (raw)
In-Reply-To: <>

Hi Felipe, 

> Le 13 nov. 2020 à 01:47, Felipe Contreras <> a écrit :
> On Fri, Nov 13, 2020 at 12:02 AM D.E. Goodman-Wilson
> <> wrote:
>>> Did we hear the testimony of a single black person that was offended
>> by the word?
>>> Nobody affected by this change actually asked for this change
>> Five minutes searching Twitter will reveal a great number of Black git users championing this change.
> This is anecdotal evidence.
> We all live in our own digital bubble. Every person's Twitter feed is
> different, and Google search results depend on where you live, and
> your past searches.
> You may find "a great number" of users that match that criteria, what
> I find is only people criticizing the move, and after five minutes I
> haven't found a single black person actually offended by the current
> name.
>> How is reopening this discussion anything but a distraction?
> This discussion never happened.
> Everyone in the June thread argued about the different names of the
> potential branch, and the culture war implications. Virtually *nobody*
> argued about the manner of implementation: deprecation period, clear
> warnings, Git 3.0 consideration.

I couldn't agree more. We really need to be warning users several versions in advance,
and I mean months or even years. I don't wan't to come up with a number, but I would
guess that maybe 85 %, (or even 95 % ?) of the world-wide Git user base is unaware that any discussion
on that topic ever took place.

Brian mentioned that some people voicing their concern on the list did not abide by the code of conduct. 
There was also very vocal disagreement voiced in the Git-for-Windows GitHub project before the
discussion reached the mailing list, of which a lot was also considered to not abide by that project's
code of conduct. While I agree that discussion should be done with respect, and some people that 
are driven to react to such important changes might not be aware of any code of conduct they should 
follow, because they don't participate in the "day-to-day" life of the project, just the fact that they even
care enough to voice their disagreement should be a big red flag in terms of how this change should be done,
in my opinion.

I had avoided commenting on this whole subject, but the main point you are bringing, 
that such a change, if done, should be made with great care to our user base and a lot 
more warning, is a very important one. 

Thanks for bringing it up.


  reply	other threads:[~2020-11-13 13:54 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
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]     ` <>
2020-11-13  6:47       ` Felipe Contreras
2020-11-13 13:53         ` Philippe Blain [this message]
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:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link list mirror (unofficial, one of many)

This inbox may be cloned and mirrored by anyone:

	git clone --mirror
	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/ \
	public-inbox-index git

Example config snippet for mirrors.
Newsgroups are available over NNTP:
 note: .onion URLs require Tor:

code repositories for the project(s) associated with this inbox:

AGPL code for this site: git clone