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

[Felipe Contreras <felipe.contreras@gmail.com>]

On Thu, Nov 12, 2020 at 11:14 PM Theodore Y. Ts'o <tytso@mit.edu> wrote:

> Is it changing the default branch name when creating a new repository?
> (Which affects only people creating new repositories)

You may choose to downplay the experience of certain part of the
user-base, because in your experience creating new repositories
doesn't happen often, but that doesn't mean these users don't exist.

Yes, this is the part I'm concerned about.

At this very moment there's people in universities trying to learn Git
and creating repositories, so are people training in companies.
There's a whole industry dedicated to teaching Git, and they rely on
creating repositories.

A simple "git grep master" on the documentation of git.git (without
the release notes) shows at least 800 instances.

This is precisely the part that was neglected in the v1.6.0 release
that I undertook: nobody bothered to change the documentation that was
using git-foo commands.

I find it curious that this is the criticism you choose to give on a
change that is supposed to be making Git more inclusive towards people
with different experiences (potentially non-existent); making light of
the experiences of very real people which we know exist.

Shouldn't we be inclusive towards these very real users as well?

Since this is 2020, and just to be crystal clear: I intend no offense,
I just truly find this argument curious.

Cheers.

-- 
Felipe Contreras