On Wed, 18 Jul 2018 13:47:03 +0100 "M. J. Everitt" <[email protected]> wrote:
> - Line one is limited to <cat>/<pkg> and some Key Word that defines > the type of change made, similar to bugzilla perhaps eg. "REVBUMP, > VERBUMP, EAPIBUMP, BUGFIX, PATCH, FEATUREREQ, OTHER". This would get > around the issue of long package-names and/or overlays and other > lengthy prefixes. Hell no. I want to see as *much* data as possible in the limited summary, not the *LEAST*. That's why we have this problem in the first place: Developers are trying *HARD* to put sufficiently quality information. This proposal as-is basically champions the line length limitation to absurdity. If you go down this road you may as well "Fix" the problem by forcing everyone to make the commit summary the shortened SHA1 of the rest of the text in the commit message.... at least that way you're *GUARANTEED* to never exceed 50 odd characters. The commit summary will be useless, but hey, we got that message length down alright. Yay!
pgpd2migo1z58.pgp
Description: OpenPGP digital signature
