On 2026-01-26 19: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?
It is probably better to do it now, as there hasn't been much new development yet. Since 2.3.0 isn't much different from the previous versions, I don't think that 2.3.x will receive many patches. > > 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. You could also ban trailing whitespace after "\" since this is not portable. -- Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / Pascaline project (LIP, ENS-Lyon)
