From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: nnimap ?
Date: 10 Sep 1999 18:17:06 +0200 [thread overview]
Message-ID: <vaf906e2131.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: Sam Falkner's message of "10 Sep 1999 10:01:34 -0600"
Sam Falkner <samf@central.sun.com> writes:
> Are there any plans to integrate this into gnus itself ...
Yes.
> ... anytime soon?
Who's to know? Simon says he wants to release nnimap 1.0 rather
soonish. (Only bugfixes, no new features.) After nnimap 1.0 has been
released, it can presumably be incorporated into Gnus.
In the meantime, the current Gnus and nnimap work together just fine
-- there is a quirk every now and then, but the added productivity of
Gnus more than makes up for that.
kai
--
I like BOTH kinds of music.
next prev parent reply other threads:[~1999-09-10 16:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-09 22:16 funky funky Topics and kill/yank groups Jack Vinson
1999-09-10 5:28 ` nnimap ? Jens-Ulrik Petersen
1999-09-10 9:55 ` Kai Großjohann
1999-09-10 16:01 ` Sam Falkner
1999-09-10 16:17 ` Kai Großjohann [this message]
1999-09-10 9:55 ` funky funky Topics and kill/yank groups Kai Großjohann
1999-09-25 8:48 ` Lars Magne Ingebrigtsen
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=vaf906e2131.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--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).