[arch-projects] [devtools] [PATCH] commitpkg: Avoid excess blank lines

Eli Schwartz eschwartz at archlinux.org
Tue Sep 17 14:34:15 UTC 2019

On 9/17/19 9:30 AM, Daniel M. Capella via arch-projects wrote:
> Most of the time we're just bumping the pkgver and checksums, where a
> commit body isn't needed.
> Referencing commit ee970f0bde3c90a0dff909c366d4ab1a1bff9b9d

I religiously use the additional message "upstream release" in such cases.

This is important information. When there is *no* commit message, I know
that the person who committed the change is a person who dislikes commit
messages. When there is a commit message and it says 'upstream release'
or 'bump version' or whatever, then I know they put some thought into
what they're saying, and there is genuinely nothing else to say.


Given the original intent of the commit message was, explicitly, "let's
use commit messages and insert a couple newlines so that the committer
is ready for the commit message", I'm quite sure I don't understand your
rationale at all.

The only thing wrong with the commitpkg template is that it doesn't have
editor-specific methods for starting with the cursor at the third line.

Eli Schwartz
Bug Wrangler and Trusted User

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 1601 bytes
Desc: OpenPGP digital signature
URL: <https://lists.archlinux.org/pipermail/arch-projects/attachments/20190917/3e36ca01/attachment.sig>

More information about the arch-projects mailing list