From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] improvement: add self as recipient on crypted sent messages
Date: Sun, 02 Nov 2008 11:30:54 -0800 [thread overview]
Message-ID: <1225654227-sup-7841@entry> (raw)
In-Reply-To: <7tCX6GnV.1225386225.8453510.tpo2@192.168.3.7>
Reformatted excerpts from Tomas Pospisek ML's message of 2008-10-30:
> Patch is below. Two comments:
Applied, thanks!
> 1. is there a less ugly way to create a new Array with an additional
> element?
Nope, that's the right way.
> 2. the patch assumes that adding "From: " to gpg's" --recipient"s is a
> sensible thing to do and thus it does it with no questions asked
Seems reasonable to me.
--
William <wmorgan-sup at masanjin.net>
prev parent reply other threads:[~2008-11-02 19:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 13:57 [sup-talk] improvement: add self as recipient on " Tomas Pospisek ML
2008-10-30 17:03 ` [sup-talk] improvement: add self as recipient on crypted " Tomas Pospisek ML
2008-11-02 19:30 ` William Morgan [this message]
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=1225654227-sup-7841@entry \
--to=wmorgan-sup@masanjin.net \
/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