Re: What will come after Git 2.56?

["Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com>]

On Thu, Sep 24, 2026, at 20:35, Harald Nordgren wrote:
>> 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?

Changing defaults is difficult. The code changes might be small but you
have to convince many people that the potential disruption is worth it.

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.

I have of course seen this idea on this list before.