Ludovic Courtès <l...@gnu.org> writes: > It seems doable, yes. (I’d personally miss the ability to search for an > identifier in the commit log, but the overall tradeoff on a social level > seems favorable to me.)
I mentioned some additional log filtering options in [my reply to Tomas]. Not a drop-in replacement, exactly, but worth having in your toolbox! >> What about the double spaces convention? Would you favor dropping it >> as well? > > I don’t think that’s related, is it? I think few of us care whether > people use two spaces in commit messages, but I’d personally be more > picky in text snippets because I find it clearer… I personally have a hard time justifying the style based on perceived clarity when so few projects require it anymore. I discuss it more in [the message Maxim replied to]. To me, the commit message format and double spaces in the source both fit under the umbrella of “improving first-time contributor experience” and “reducing review noise”. I share the [Linux docs maintainer’s point of view, FWIW]: > for docs in general, I’m absolutely uninterested in patches adjusting > the number of spaces after periods. It really doesn’t matter one way > or the other, and I don’t think we benefit from that kind of churn. That said… > Maybe the greatest common denominator (ah ha!) is a proposal to change > commit messages, where people are free to choose between two-spaces or > not? …if people feel strongly about the double spaces in project sources, I think revisiting the commit messages would still be a great start 😀. —Liam [my reply to Tomas] <https://yhetil.org/guix-devel/87o6tsbpqm....@hpfr.net> [the message Maxim replied to] <https://yhetil.org/guix-devel/877c0lck2x....@hpfr.net> [Linux docs maintainer’s point of view, FWIW] <https://lore.kernel.org/linux-doc/20180808072310.4695c...@lwn.net/>
