Re: js/init-defaultbranch-advice, was Re: What's cooking in git.git (Dec 2020, #01; Tue, 8)

[Junio C Hamano <gitster@pobox.com>]

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

> On Wed, 9 Dec 2020, Junio C Hamano wrote:
>
>> Anyway, I do not think those users who said "I'm fine with it" would be
>> fine when the switchover happens outside their control.
>
> As of September 29th, Git for Windows' installer asks users to specify
> their preferences:
>
> 	Adjusting the name of the initial branch in new repositories
>
> 	What would you like Git to name the initial branch after
> 	"git init"?
>
> 	[ ] Let Git decide
>
> 	    Let Git use its default branch name (currently: "master")
> 	    for the initial branch in newly created repositories.
> 	    The Git project intends to change this default to a more
> 	    inclusive name in the near future.
>
> 	[ ] Override the default branch name for new repositories
>
> 	    NEW! Many teams already renamed their default branches;
> 	    common choices are "main", "trunk" and "development".
> 	    Specify the name "git init" should use for the initial
> 	    branch:
>
> 	    __________________________
>
> Obviously, I have no idea how many users chose the first option because we
> do not collect any usage data in the Git for Windows project. However,
> anecdotal data suggests that most users go with the first one, not caring
> one iota and simply going with what Git decides for them.

Even if you knew the numbers, it would not give us much useful
information (besides, I do not think you give these checkboxes
randomized to suppress bias), I am afraid.  The users haven't
experienced the real impact of letting Git decide yet, and do not
have enough information to assess their future grief before making
the choice between the two.

But I do not strongly care---I certainly care about this even less
than I care about keeping the differences between Git and its
Windows port smaller.