From: Miles Bader <miles@gnu.org>
Cc: ding@gnus.org
Subject: Re: Moving files from lisp/gnus/ to lisp/net/?
Date: Fri, 15 Oct 2004 19:27:05 -0400 [thread overview]
Message-ID: <20041015232705.GA5196@fencepost> (raw)
In-Reply-To: <ilu1xfzwz6q.fsf@latte.josefsson.org>
On Fri, Oct 15, 2004 at 09:37:01PM +0200, Simon Josefsson wrote:
> > I also propose to add password.el, encrypt.el from Gnus CVS, and
> > update the netrc.el file to use encrypt.el. This may be more
> > controversial, so I'll post encrypt.el in a separate message, to ask
> > for guidance.
>
> I didn't realize Ted already posted encrypt.el, so let's move that
> discussion to that thread.
BTW, the Gnus CVS trunk now contains both "encrypt.el" and "gnus-encrypt.el",
which are exactly the same except that the latter uses "gnus-" prefixes for
everything (and has a big commented-out section).
Can't you just delete gnus-encrypt.el?
Thanks,
-Miles
--
`The suburb is an obsolete and contradictory form of human settlement'
next parent reply other threads:[~2004-10-15 23:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ilu655bwzng.fsf@latte.josefsson.org>
[not found] ` <ilu1xfzwz6q.fsf@latte.josefsson.org>
2004-10-15 23:27 ` Miles Bader [this message]
2004-10-16 2:08 ` 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=20041015232705.GA5196@fencepost \
--to=miles@gnu.org \
--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).