[PATCH] doc: clarify that --encrypt refers to public key encryption

Daniel Kahn Gillmor dkg at fifthhorseman.net
Thu Nov 30 16:25:39 CET 2017

On Wed 2017-11-22 09:52:05 +0100, Werner Koch wrote:
> On Tue, 21 Nov 2017 17:15, dkg at fifthhorseman.net said:
>> OK, pushed a modified/clarified form to master.  Should this also be
>> backported to the stable branches?
> Yes. 

pushed to 2.2, thanks for the followup.

> On Monday's telco we agreed on that clear bug fixes (and I would also
> say doc fixes) should be done to the 2.2 branch and then merged by the
> hacker on duty into master within the next few days.
> All changes for which it is not clear whether they need to go into 2.2
> are to be done in master and will be cherry-picked into 2.2 on a case to
> case base.

This sounds like sensible policy.  Thanks for spelling it out here.

is there an explicit role or rotation for "hacker on duty" that i should
know about?  Pointers to existing documentation are welcome.

All the best,

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <https://lists.gnupg.org/pipermail/gnupg-devel/attachments/20171130/8f5f6a17/attachment.sig>

More information about the Gnupg-devel mailing list