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

Re: Consensus on a new default branch name

From
Jeff King <peff@peff.net>
Date
Jun 16, 2020, 14:38 UTC
Message-ID
<20200616143816.GN666057@coredump.intra.peff.net>
In-Reply-To
<20200616022239.GD164606@google.com>
On Mon, Jun 15, 2020 at 07:22:39PM -0700, Jonathan Nieder wrote:
> In Git, we make most decisions by a rough consensus of active
> contributors, as judged by the maintainer.[...]

Thanks for writing this out. I agree completely with how you described the decision making process.

We do bear the responsibility to think carefully about our users, and to respect their time, and their expectations that things don't break. But as with any feature, it's a juggling act between stability and progress that developers and the maintainer must deal with. Somebody might not care about this name change, but likewise, others might not care about a particular technical feature. At some point users have to put their trust in Git's developers that the end product will be stable and useful. If we break that trust too much, then forking is an option, as you note. Our track record has been pretty good so far, and I think if we approach this change carefully, it can continue to be.

-Peff
Previous: Taylor Blau
Message 4 of 4 in “Re: Consensus on a new default branch name”
  1. Nomen NescioJun 16, 2020
  2. Jonathan NiederJun 16, 2020
  3. Taylor BlauJun 16, 2020
  4. Jeff KingJun 16, 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.