[PATCH] handle disambiguation of --throw-keyids more cleanly

Daniel Kahn Gillmor dkg at fifthhorseman.net
Mon Nov 24 17:30:44 CET 2014

On 11/24/2014 03:42 AM, Werner Koch wrote:
> On Fri, 21 Nov 2014 23:25, dkg at fifthhorseman.net said:
>> Dropping the shorter version shouldn't change any behavior currently
>> in use, since --throw-keyid should be treated as an unambiguous prefix
>> to --throw-keyids, and is now more consistent with other argument
>> disambiguation handling.
> Not really.  The full name is required in the conf files.

so is --throw-keyid just an older variant of the command?  Do we plan to
keep it around forever?

It seems like we should choose one of these approaches for long-term

 a) deprecate --throw-keyid now and make plans to remove it in the
future, or
 b) remove throw-keyid but make it produce an error when found in the
config file
 c) go ahead and remove throw-keyid entirely  as we transition to 2.1,
where several other minor changes are happening.

fixing a config file "throw-keyid" to "throw-keyids" isn't a difficult
change, and it's only likely to be relevant for a very small number of


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 949 bytes
Desc: OpenPGP digital signature
URL: </pipermail/attachments/20141124/34a8d796/attachment.sig>

More information about the Gnupg-devel mailing list