Someone recently warned me of using a too long commit message that wasn't complying GLEP 66, that defines that summary shouldn't be too long and we should rely on "body" for longer messages: https://www.gentoo.org/glep/glep-0066.html#id8 The problem is that needing to use EDITOR all the time for that has some drawbacks, the first case that came to my mind was when the commit message is the same for multiple commits affecting different packages. Currently that is easy simply relying on bash history... but needing to go always into EDITOR would force me to copy&paste the message all the time and also manually edit the package name (that now is set automatically when run from command line directly). I could rely on creating a temporal file with a commit message and rely on -M option... but needing to create that temporal file with the commit message every time looks overkill to me. Then, I would suggest to split current -m into two options following the sames GLEP 66 uses to describe this: --summary and --body --summary would have a character limitation (current -m would be kept for compatibility but would be the same as --summary to prevent long messages to be committed --body could be used to pass the extra message without that constraints Thanks
repoman support has been removed per bug 835013. Please file a new bug (or, I suppose, reopen this one) if you feel this check is still applicable to pkgcheck and doesn't already exist.
pkgcheck will let you use -m twice.
