[PATCH libgpg-error] doc: clarify patch submission workflow

Damien Goutte-Gattat dgouttegattat at incenp.org
Thu Feb 1 17:20:25 CET 2018


On 02/01/2018 01:24 PM, Thorsten Behrens wrote:
> +  - send your patches to that list, preferably PGP/MIME signed.

As far as I know, git send-email does not allow to do that. (Or if it 
does, I never found how to do it--when I looked for that feature, I 
found nothing else than an a old bug report complaining precisely that 
it was not supported [1].)

It seems strange to ask for "preferably PGP/MIME signed" patches and to 
suggest a workflow which does not support it.


[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=534251

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20180201/81f5ebad/attachment.sig>

More information about the Gnupg-devel mailing list