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

From: Lukasz Niemier <lukasz.niemier@kobil.com>
Date: Nov 14, 2020, 14:19 UTC
Message-ID: <CBC2DBAA-A409-49CD-B932-AC82D3C20D55@kobil.com>
In-Reply-To: <20201113145802.GB3985404@mit.edu>

Show 9 quoted lines

> OK, fine.  That wasn't clear in your earlier messages.  So this is
> *not* like 2008, where we are breaking workflows or finger macros of
> *existing* git users.
> 
> Instead, we might be causing a certain amount of confusion with
> respect to *new* users, especially if some portion of them are using
> an older version of git, where the default initial branch name is
> "master", or a newer version of git, where the default initial branch
> name is "main".

I am pretty much **existing** Git user where I am maintaining few repos yet I am constantly creating new ones for another projects of mine. Such abrupt change in the default branch name, without any warning, would be very confusing for me. Not every user is working on a single Git repo for their whole life.

I feel that our view on who is **new** or **existing** user differs.

--

Łukasz Niemier lukasz.niemier@kobil.com