From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: nnml is diverging from other backends
Date: Sat, 18 Aug 2001 21:29:59 +0200 [thread overview]
Message-ID: <m3wv41dv48.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <vafae0xi8ba.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de>
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> I notice that nnml is diverging from the other nnmail-derived backends
> right now. Maybe too few people care about the other backends... Do
> you think we should just let it slide, or should the new functionality
> from nnml be copied to the other backends, too?
It should be copied, but perhaps our efforts are best spent
elsewhere. I mean, nobody uses nnbabyl and few use nnmbox. nnfolder
has users, and nnimap has a rapidly growing number of users. But nnml
is the mail backend that most people use, so I think it makes sense
that it is the most feature complete mail backend...
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2001-08-18 19:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-18 17:31 Kai Großjohann
2001-08-18 19:11 ` Jody Klymak
2001-08-18 19:45 ` Harry Putnam
2001-08-18 19:29 ` Lars Magne Ingebrigtsen [this message]
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=m3wv41dv48.fsf@quimbies.gnus.org \
--to=larsi@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).