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

Re: What will come after Git 2.56?

From
Harald Nordgren <haraldnordgren@gmail.com>
Date
Sep 24, 2026, 18:35 UTC
Message-ID
<20260924183523.53201-1-haraldnordgren@gmail.com>
In-Reply-To
<ap50kgyenpRrsqln@pks.im>
> Well, same as there's room after Git 2.9 we also still have room after
> Git 2.99. No reason we cannot have Git 2.100. :)

I agree completely, no need signal that 3.0 is coming until it comes. Once it's out, not a soul will question what number the release just before had.

I have a list of breaking changes that I would like to introduce, I was hoping they could be considered before 3.0 is out -- otherwise I fear I have to wait another 10 years for 4.0, I would like to change the default values of these config values:

    # Autostash by default
    checkout.autostash=true
    rebase.autostash=true
    # User friendlier branch sorting
    branch.sort=-committerdate
    tag.sort=-version:refname
    # Better diffing
    diff.algorithm=histogram
    diff.colormoved=zebra
    diff.compactionheuristic=true
    # Compare branches on when push/upstream are different
    status.comparebranches=@{upstream} @{push}

It seemed a bit presumptuous to submit these as a patch, but maybe I should to open the formal discussion?

Harald  
Previous: Patrick SteinhardtNext: Junio C Hamano
Message 4 of 13 in “What will come after Git 2.56?”
  1. Junio C HamanoSep 6, 2026
  2. brian m. carlsonSep 6, 2026
  3. Patrick SteinhardtSep 7, 2026
  4. Harald NordgrenSep 24, 2026
  5. Junio C HamanoSep 24, 2026
  6. Changing default config values (was Re: What will come after Git 2.56?)Phillip Wood, Sep 27, 2026
  7. Junio C HamanoSep 27, 2026
  8. Jeff KingSep 28, 2026
  9. Kristoffer HaugsbakkSep 25, 2026
  10. D. Ben KnobleSep 25, 2026
  11. Emily ShafferSep 7, 2026
  12. rsbecker@nexbridge.comSep 8, 2026
  13. brian m. carlsonSep 8, 2026

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.