From: itaylor@uark.edu (Ian Taylor)
Subject: [sup-talk] [PATCH] gpg exact match
Date: Tue, 20 May 2008 21:39:03 -0400 [thread overview]
Message-ID: <1211333682-sup-5934@red> (raw)
I think gnupg developers made a poor choice for the --recipient option,
so this patch is needed.
### FROM GPG MAN PAGE ###
HOW TO SPECIFY A USER ID
...
By exact match on an email address.
This is indicated by enclosing the email address in the usual way with
left and right angles.
<heinrichh at uni-duesseldorf.de>
...
By substring match.
This is the default mode but applications may want to explicitly
indicate this by putting the asterisk in front. Match is not case
sensitive.
Heine
*Heine
##########################
The problem arose when a friend of mine was trying to send a mail to me
brian at lorf.org -> ian at lorf.org
Instead of using me for a recipient, it was using him.
The supplied patch should fix this behavior.
--
Ian Taylor
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-exact-match-gpg-fix.patch
Type: application/octet-stream
Size: 909 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/sup-talk/attachments/20080520/ffda8fc4/attachment.obj>
next reply other threads:[~2008-05-21 1:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-21 1:39 Ian Taylor [this message]
2008-05-25 2:19 ` William Morgan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1211333682-sup-5934@red \
--to=itaylor@uark.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox