Gnus development mailing list
 help / color / mirror / Atom feed
From: "Ted Zlatanov" <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: pop3.el itegration with netrc.el
Date: 15 Oct 2004 15:07:25 -0400	[thread overview]
Message-ID: <4noej394wi.fsf@lifelogs.com> (raw)
In-Reply-To: <ilu8ya7yj0v.fsf@latte.josefsson.org> (Simon Josefsson's message of "Fri, 15 Oct 2004 19:43:12 +0200")

On Fri, 15 Oct 2004, jas@extundo.com wrote:

> Perhaps there should be some autoload cookies in encrypt.el, to
> avoid the autoload declarations inside netrc.el.

Done, I think (I didn't remove the autoload declarations in netrc.el
yet though).

All the changes are in CVS now.

> Would gnus-encrypt.el still be useful?

I don't think so, so I've mentally marked it for tentative removal.
If no complaints arise I'll remove it next week.

> I'd say we can maintain them in Gnus CVS, and sync the version in
> Emacs from time to time.
> 
> When you have installed the files in Gnus HEAD, I'll write a proposal
> to install them in Emacs CVS on emacs-devel, and install them if
> nobody object.  Since it is new functionality, I'm assuming they
> shouldn't go into Gnus 5.10.  Hopefully by moving the files away from
> emacs/lisp/gnus/ the auto-sync gateway won't merge the files back into
> Gnus 5.10.

I have a feeling a lot of people will have something to say about
encrypt.el - it's a touchy topic for a lot of developers, and it's
hard to do it right.

Ted



  reply	other threads:[~2004-10-15 19:07 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-13 15:44 Ted Zlatanov
2004-10-14 18:21 ` Simon Josefsson
2004-10-14 18:37   ` Ted Zlatanov
2004-10-14 18:56     ` Simon Josefsson
2004-10-14 18:49   ` Reiner Steib
2004-10-14 19:01     ` Simon Josefsson
2004-10-14 19:52       ` Reiner Steib
2004-10-14 22:39         ` Simon Josefsson
2004-10-15 17:08           ` Ted Zlatanov
2004-10-15 17:43             ` Simon Josefsson
2004-10-15 19:07               ` Ted Zlatanov [this message]
2004-10-15 19:16               ` Reiner Steib
2004-10-17 23:13                 ` Miles Bader
2004-10-18 18:30                   ` Ted Zlatanov
2004-10-21 18:35                     ` Ted Zlatanov
2004-10-15 18:07             ` Reiner Steib
2004-10-15 19:14               ` encrypt.el (was: pop3.el itegration with netrc.el) Ted Zlatanov
     [not found]                 ` <iluwtxrvkfb.fsf@latte.josefsson.org>
     [not found]                   ` <E1CIozF-00034v-V7@fencepost.gnu.org>
     [not found]                     ` <4n4qkrvrwu.fsf@lifelogs.com>
     [not found]                       ` <E1CJx6h-0000Ns-QW@fencepost.gnu.org>
     [not found]                         ` <4nsm87vrgk.fsf@lifelogs.com>
     [not found]                           ` <4nr7m9j1ah.fsf@lifelogs.com>
2004-12-01 22:12                             ` encrypt.el Reiner Steib
2004-12-02 16:36                               ` encrypt.el Ted Zlatanov
2004-12-02 20:56                                 ` encrypt.el Reiner Steib
2004-12-07 17:50                                 ` encrypt.el Ted Zlatanov
2004-10-15 17:48           ` pop3.el itegration with netrc.el Reiner Steib
2004-10-15 17:58             ` Simon Josefsson
2004-10-15 18:55               ` Reiner Steib
2004-10-17 23:22             ` Miles Bader

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=4noej394wi.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).