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

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

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 10, 2020, 18:33 UTC
Message-ID
<xmqqeejxwlx9.fsf@gitster.c.googlers.com>
In-Reply-To
<nycvar.QRO.7.76.6.2012100540220.25979@tvgsbejvaqbjf.bet>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
Show 33 quoted lines
> 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.

Previous: Johannes SchindelinNext: Felipe Contreras
Message 27 of 30 in “What's cooking in git.git (Dec 2020, #01; Tue, 8)”
  1. Junio C HamanoDec 9, 2020
  2. Taylor BlauDec 9, 2020
  3. Jonathan TanDec 10, 2020
  4. Elijah NewrenDec 9, 2020
  5. Junio C HamanoDec 9, 2020
  6. Taylor BlauDec 9, 2020
  7. Junio C HamanoDec 10, 2020
  8. Jonathan TanDec 10, 2020
  9. fc/pull-merge-rebase, was Re: What's cooking in git.git (Dec 2020, #01; Tue, 8)Johannes Schindelin, Dec 9, 2020
  10. Junio C HamanoDec 9, 2020
  11. Felipe ContrerasDec 10, 2020
  12. Johannes SchindelinDec 10, 2020
  13. Johannes SchindelinDec 10, 2020
  14. Felipe ContrerasDec 10, 2020
  15. Theodore Y. Ts'oDec 10, 2020
  16. Junio C HamanoDec 10, 2020
  17. Felipe ContrerasDec 11, 2020
  18. Junio C HamanoDec 11, 2020
  19. Theodore Y. Ts'oDec 11, 2020
  20. Felipe ContrerasDec 12, 2020
  21. Felipe ContrerasDec 11, 2020
  22. Felipe ContrerasDec 10, 2020
  23. Junio C HamanoDec 11, 2020
  24. js/init-defaultbranch-advice, was Re: What's cooking in git.git (Dec 2020, #01; Tue, 8)Johannes Schindelin, Dec 9, 2020
  25. Junio C HamanoDec 9, 2020
  26. Johannes SchindelinDec 10, 2020
  27. Junio C HamanoDec 10, 2020
  28. Felipe ContrerasDec 11, 2020
  29. bc/rev-parse-path-format, was Re: What's cooking in git.git (Dec 2020, #01; Tue, 8)Johannes Schindelin, Dec 10, 2020
  30. Junio C HamanoDec 10, 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.