Gnus development mailing list
 help / color / mirror / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org, emacs-devel@gnu.org
Subject: Re: imap.el and nnimap.el
Date: Mon, 14 Feb 2011 15:17:22 -0500	[thread overview]
Message-ID: <pyfwrqjrql.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <87hbc6vf69.fsf@lifelogs.com> (Ted Zlatanov's message of "Mon, 14 Feb 2011 08:55:42 -0600")

Ted Zlatanov wrote:

> Are there special warning when you use obsolete things?

Yes, you get a warning when loading something from obsolete/.

> Gnus itself needs imap.el only in one place (mail-source.el) so I
> propose we move imap.el to Emacs and out of Gnus when and if that
> dependency is removed.  It's a general-purpose library anyway.

Sounds good to me. It's already in the net/ directory in Emacs, so from
the Emacs side there would be nothing to do. Just stop syncing it
to/from Gnus I guess.



  parent reply	other threads:[~2011-02-14 20:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AANLkTikV=nnEFB03UYH-tcMNEDGRbqcVQ6683p3CUwUK@mail.gmail.com>
     [not found] ` <8762sn4fgh.fsf@lifelogs.com>
     [not found]   ` <v6oc6fe7g9.fsf@fencepost.gnu.org>
     [not found]     ` <87tyg72wrl.fsf@lifelogs.com>
     [not found]       ` <fir5bbe2x0.fsf_-_@fencepost.gnu.org>
2011-02-14 14:55         ` imap.el and nnimap.el [was Re: Build failure bzr trunk revno 103260] Ted Zlatanov
2011-02-14 19:45           ` Lars Ingebrigtsen
2011-02-14 19:47             ` Lars Ingebrigtsen
2011-02-14 20:52             ` Ted Zlatanov
2011-02-14 21:13               ` Lars Ingebrigtsen
2011-02-14 21:28                 ` Ted Zlatanov
2011-02-14 22:11                   ` Lars Ingebrigtsen
2011-02-14 20:17           ` Glenn Morris [this message]
2011-02-14 20:48             ` imap.el and nnimap.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=pyfwrqjrql.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=tzz@lifelogs.com \
    /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).