From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: emacs->gnus merge questions
Date: Tue, 11 Dec 2007 10:22:50 -0600 [thread overview]
Message-ID: <868x41jj51.fsf@lifelogs.com> (raw)
In-Reply-To: <v94petj7t6.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Sat, 08 Dec 2007 20:38:29 +0100")
On Sat, 08 Dec 2007 20:38:29 +0100 Reiner Steib <reinersteib+gmane@imap.cc> wrote:
RS> On Sat, Dec 08 2007, Miles Bader wrote:
>> I'm doing the back-merge from the Emacs trunk to the Gnus trunk.
>>
>> There are some changes which may or may not be appropriate for Gnus:
>>
>> (1) deleted: encrypt.el
RS> I'm not sure about this one. Ted?
It would be great if it could stay somewhere, maybe under contrib/
because I know at least 2 people use it. Also, can we have a
conditional use in netrc.el if it's loaded? I don't want to redefine
netrc functionality as well for everyone that wants to use it.
If it can stay, I'll need to change its library requirements from
password to password-cache as previously discussed.
Ted
next prev parent reply other threads:[~2007-12-11 16:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-08 3:24 Miles Bader
2007-12-08 19:38 ` Reiner Steib
2007-12-08 21:19 ` Miles Bader
2007-12-08 21:29 ` Reiner Steib
2007-12-08 23:32 ` Miles Bader
2007-12-08 23:45 ` Miles Bader
2008-02-16 13:24 ` encrypt.el (was: emacs->gnus merge questions) Reiner Steib
2008-02-16 13:26 ` assistant.el " Reiner Steib
2007-12-11 16:22 ` Ted Zlatanov [this message]
2007-12-17 23:02 ` emacs->gnus merge questions Ted Zlatanov
2007-12-17 23:03 ` Ted Zlatanov
2007-12-18 20:25 ` Ted Zlatanov
2007-12-18 22:52 ` encrypt.el glue to PGG library added (was: emacs->gnus merge questions) Ted Zlatanov
2008-02-16 13:12 ` encrypt.el " Reiner Steib
2008-02-28 14:55 ` encrypt.el Ted Zlatanov
2008-02-28 20:28 ` encrypt.el Reiner Steib
2008-03-10 15:06 ` encrypt.el Ted Zlatanov
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=868x41jj51.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--cc=ding@gnus.org \
/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;
as well as URLs for NNTP newsgroup(s).