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

Re: What will come after Git 2.56?

From
D. Ben Knoble <ben.knoble@gmail.com>
Date
Sep 25, 2026, 16:42 UTC
Message-ID
<CALnO6CBhWKdHFhGCycCVWrc+3WH7TCNcqy8EzmYxxOhdHvz=Fw@mail.gmail.com>
In-Reply-To
<0aaab5ec-d488-421f-b99a-330c1a851fb0@app.fastmail.com>

On Thu, Sep 24, 2026 at 9:21 PM Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com> wrote:

>
> On Thu, Sep 24, 2026, at 20:35, Harald Nordgren wrote:
[snip]
Show 9 quoted lines
> On the other hand, or on the opposite side of the spectrum, a tool that
> can read your configuration and recommend better settings would be more
> difficult to implement but could be easier to get buy-in for. This would
> be the next step up from hardcore Git users and folklore spreading
> through blogs and whatnot, thousands of users setting their version
> controlled (of course!?) global Git config one advice and word of mouth
> at a time. Just a plain old program that reads what you have, makes a
> report on the tiny little part that modern Git practice has an opinion
> on, and recommends the modern alternatives.
"git config upgrade" or something would be pretty nice :)
-- 
D. Ben Knoble
Previous: Kristoffer HaugsbakkNext: Emily Shaffer
Message 10 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.