From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: gnus-group-clear-data-on-native-groups clears nnml too
Date: 10 Oct 1996 23:19:36 +0100 [thread overview]
Message-ID: <x6aftu4g3r.fsf@eyesore.no> (raw)
In-Reply-To: Steven L Baur's message of 07 Oct 1996 14:48:14 -0700
Steven L Baur <steve@miranova.com> writes:
> Ouch! nnml groups should not be tied to an nntp server. nnml
> groups also should not have their readedness information/marks,
> etc. cleared if the group is (accidentally) unsubscribed.
>
> I would propose an additional control file (.groupinfo) to go along
> with .overview in each nnml group to fix both problems.
You mean that the backend should also store what messages have been
read and so on? Well, that would make sense, I guess. Once labels
(and stuff) have been implemented, this'll be easy enough to add.
--
"Yes. The journey through the human heart
would have to wait until some other time."
next prev parent reply other threads:[~1996-10-10 22:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-10-07 15:18 Wesley.Hardaker
1996-10-07 21:48 ` Steven L Baur
1996-10-10 22:19 ` Lars Magne Ingebrigtsen [this message]
1996-10-10 22:18 ` Lars Magne Ingebrigtsen
1996-10-11 6:37 ` Wesley.Hardaker
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=x6aftu4g3r.fsf@eyesore.no \
--to=larsi@ifi.uio.no \
/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).