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