Hi Kevin, On 2026-01-26T19:32:39+0800, Kevin J. McCarthy wrote: > On Mon, Jan 26, 2026 at 08:56:58AM +0100, Fabian Groffen via Mutt-dev wrote: > > Why don't you do it now, and declare 2.3.0 a "last" release that will not > > receive any updates. If there's a problem, that needs resolving that is > > too big not to easily backport to 2.3.0, just release 2.4.0. > > > > I think with the effort to get things going again, perhaps it is nice > > when all of that can be done immediately on a codebase that's formatted > > in the way it should be. > > I'm willing to consider doing it now. Traditionally, stable branch releases > are just for security issues and important bug fixes. I try to keep the > changes small, so while there might be some pain in merges it's probably not > insurmountable. > > How do others feel?
I don't mind. If a patch has exclusively white-space changes, it should be relateively safe, and git-diff(1) has -w to verify that it doesn't change anything other than white space. Either way should be fine, IMO. Have a lovely day! Alex > > > A commit hook can perhaps even ban commits to source/header files with > > lines that start with whitespace containing hard tabs in them. > > Yup, that would be nice. > > -- > Kevin J. McCarthy > GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA -- <https://www.alejandro-colomar.es>
signature.asc
Description: PGP signature
