[PATCH libgpg-error] doc: clarify patch submission workflow
dgouttegattat at incenp.org
Mon Feb 26 14:17:06 CET 2018
Hi GnuPG folks,
On 02/04/2018 04:55 AM, Todd Zullinger wrote:
> Another option might be to recommend that users generate
> patches with git format-patch² and then process them using
> another script which can PGP/MIME sign them.
> I don't know if there's already a convenient script to
> create PGP/MIME messages or not.
Several years ago, I wanted to understand how MIME messages are
constructed and I wrote a small program that can take a message body and
turn it into a PGP/MIME-signed message.
I forgot about this program almost as soon as I finished it. The above
discussion reminded me of it. As it turns out, this program could be
used for the purpose described by Todd.
The program is called fmail and may be found on my homepage . It
reads a message (such as one produced by git format-patch) on its
standard input and, if called with the -s option, emits a
PGP/MIME-signed message on its standard output. The signed message may
then be sent with presumably any mail submission agent (I tested with
both msmtp and git send-email).
With this program, the workflow for a single patch could be the following:
$ git format-patch -1 --stdout [other format-patch options] | \
fmail -s | git send-email
And for a patch set:
$ git format-patch [format-patch options]
$ for mail in *.patch ; do fmail -s < $mail > $mail.signed ; done
$ git send-email *.signed
Note: I am *not* advocating the use of my program to send patches to
gnupg-devel (actually I don't even like advertising it here, I am doing
it now only because it happens to be relevant to the discussion). My
point is mainly that the "another option" proposed by Todd is doable.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 488 bytes
Desc: OpenPGP digital signature
More information about the Gnupg-devel