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
Felipe Contreras <felipe.contreras@gmail.com>
Date
Dec 11, 2020, 00:03 UTC
Message-ID
<CAMP44s3Wp5HfmHB2UZFJyZSVv7xE9YAKVOWfDUCGOwHtQV6Gzw@mail.gmail.com>
In-Reply-To
<xmqqeejxwlx9.fsf@gitster.c.googlers.com>
On Thu, Dec 10, 2020 at 12:38 PM Junio C Hamano <gitster@pobox.com> wrote:
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> > 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.
1. The first option says let git use "master". The user might have
stopped reading there.
2. Even if you had collected numbers, anyone with a minimal
understanding of statistics would tell you that you can't extrapolate
numbers from a subgroup of the population to the total population. You
need a random (non-biased) sample.
3. Anecdotal evidence is the weakest form of evidence.

So yeah, even if we suppose that most users (what is "most"? 51%?, 75%?, 90%?) of Git for Windows did choose the first option, we can't assume the rest of the users are going to choose that option, and for the same reason.

Something that very often happens in these types of questions is that the user simply did not understand the question, and just chose the first one.

Cheers.
-- 
Felipe Contreras
Previous: Junio C HamanoNext: Johannes Schindelin
Message 28 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.