From: Kai Grossjohann <kai.grossjohann@gmx.net>
Subject: Re: Proposed Changes
Date: Sun, 16 May 2004 15:53:52 +0200 [thread overview]
Message-ID: <86pt94iikv.fsf@slowfox.dyndns.org> (raw)
In-Reply-To: <m3wu3ch659.fsf@quimbies.gnus.org>
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Kevin Greiner <kgreiner@xpediantsolutions.com> writes:
>
>> To clarify the issue, the cache and agent were originally designed for
>> the nntp backend. As a result, they are simply ignored when non-nntp
>> commands (such as renaming a group) are performed. A number of
>> threads have reported problems with moved articles not
>> disappearing or showing the wrong content. I agree that Lars will
>> have to decide whether enhancing the cache and agent to better support
>> imap is a new feature or a bug fix.
>
> I think this sounds more like a new feature than a bug fix, actually...
I'm surprised.
OT1H extending the Agent to handle moves sounds like a new feature.
But OTOH, Gnus displaying the wrong article contents surely sounds
like a bug.
Kai
next prev parent reply other threads:[~2004-05-16 13:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-09 8:53 Gnus 5.10 and Emacs' CVS Frank Schmitt
2004-04-09 10:45 ` Sebastian D.B. Krause
2004-04-10 15:51 ` Kevin Greiner
2004-04-13 11:15 ` Proposed Changes Kevin Greiner
2004-04-13 17:51 ` Reiner Steib
2004-04-14 3:55 ` Kevin Greiner
2004-04-14 6:38 ` Kai Grossjohann
2004-04-14 16:38 ` Kevin Greiner
2004-04-14 20:00 ` Kai Grossjohann
2004-05-16 13:07 ` Lars Magne Ingebrigtsen
2004-05-16 13:53 ` Kai Grossjohann [this message]
2004-05-22 17:20 ` Lars Magne Ingebrigtsen
2004-04-09 12:48 ` Gnus 5.10 and Emacs' CVS Jesper Harder
2004-04-09 13:03 ` Henrik Enberg
2004-04-09 13:10 ` Jesper Harder
2004-04-09 15:47 ` Frank Schmitt
2004-04-09 16:13 ` Jesper Harder
2004-04-09 18:58 ` Peter Lee
2004-04-09 20:09 ` Romain Francoise
2004-04-09 20:34 ` Sebastian D.B. Krause
2004-04-09 21:58 ` Jesper Harder
2004-04-10 2:10 ` Miles Bader
2004-04-09 16:35 ` Henrik Enberg
2004-04-09 16:37 ` Henrik Enberg
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=86pt94iikv.fsf@slowfox.dyndns.org \
--to=kai.grossjohann@gmx.net \
/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).