[admin] Sending patches
Todd Zullinger
tmz at pobox.com
Thu Feb 1 17:08:48 CET 2018
Werner Koch wrote:
> Hi!
>
> this is quick note to ask you to always include a tag like [gpgme] or
> [gnupg] etc. in the subject when sending a patch.
>
> This mailing list is used for several projects and it makes the
> maintainer task easier if there is no need to guess for which project
> the patch is intended.
This can be done fairly simply when using git format-patch.
The format.subjectPrefix option can be set per repository.
For example, if I were working in a clone of gnupg.git, I
could use:
$ git config format.subjectPrefix 'PATCH/gnupg'
and then generated patches would have a subject line like:
Subject: [PATCH/gnupg] ...
Perhaps that's worth adding to https://git.gnupg.org/ or
similar?
--
Todd
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
A fool's brain digests philosophy into folly, science into
superstition, and art into pedantry. Hence University education.
-- George Bernard Shaw
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 543 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20180201/001bc519/attachment.sig>
More information about the Gnupg-devel
mailing list