git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: The master branch rename, and avoiding another v1.6.0 git-foo fiasco

From
Felipe Contreras <felipe.contreras@gmail.com>
Date
Nov 13, 2020, 06:47 UTC
Message-ID
<CAMP44s1vx==-0Sh_dN66k-u_LwUSqQRn+ckMrYMHhz7i8ZVr2Q@mail.gmail.com>
In-Reply-To
<nbCkLegnP_kb-16UzAuDChE0p68ZtRD_3ZN3o3BJHYBYpUxTWuKjvhCSKT7zRZl_sckHrkyJl2fwePFUBR-HtDcEV0rHuac6Ygg-FrrYsYI=@goodman-wilson.com>

On Fri, Nov 13, 2020 at 12:02 AM D.E. Goodman-Wilson <don@goodman-wilson.com> wrote:

Show 6 quoted lines
> > 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'd argue *that* was the distraction.

In 2008 people started multiple threads *after* the sudden change to git-foo without warning happened.

If we do the same, this discussion will happen again. I'm just the canary in the coal mine giving you a heads up.

Choosing to ignore the very real danger doesn't make the very real danger go away, you are just delaying it and making it potentially bigger. You choose to ignore the canary at your own peril. This is precisely what happened in 2008.

Cheers.
-- 
Felipe Contreras
Previous: Ismael LucenoNext: Philippe Blain
Message 22 of 25 in “The master branch rename, and avoiding another v1.6.0 git-foo fiasco”
  1. Felipe ContrerasNov 13, 2020
  2. brian m. carlsonNov 13, 2020
  3. Felipe ContrerasNov 13, 2020
  4. Theodore Y. Ts'oNov 13, 2020
  5. Felipe ContrerasNov 13, 2020
  6. Theodore Y. Ts'oNov 13, 2020
  7. Felipe ContrerasNov 13, 2020
  8. Michal SuchánekNov 13, 2020
  9. Lukasz NiemierNov 14, 2020
  10. Theodore Y. Ts'oNov 15, 2020
  11. Felipe ContrerasNov 15, 2020
  12. Brandon CaseyNov 19, 2020
  13. Peter HadlawNov 19, 2020
  14. Konstantin RyabitsevNov 19, 2020
  15. Junio C HamanoNov 19, 2020
  16. Felipe ContrerasNov 19, 2020
  17. Konstantin RyabitsevNov 20, 2020
  18. Brandon CaseyNov 19, 2020
  19. Felipe ContrerasNov 20, 2020
  20. Don Goodman-WilsonNov 13, 2020
  21. Ismael LucenoNov 20, 2020
  22. Felipe ContrerasNov 13, 2020
  23. Philippe BlainNov 13, 2020
  24. Felipe ContrerasNov 13, 2020
  25. WhinisNov 23, 2020

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.