From: Simon Josefsson <jas@extundo.com>
Cc: Lloyd Zusman <ljz@asfast.com>, ding@gnus.org
Subject: Re: Changed criteria for deciding if articles have been read?
Date: Tue, 02 Oct 2001 19:19:02 +0200 [thread overview]
Message-ID: <ilu8zeuc648.fsf@barbar.josefsson.org> (raw)
In-Reply-To: <vaf7kue9gd4.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Tue, 02 Oct 2001 18:05:59 +0200")
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> Lloyd Zusman <ljz@asfast.com> writes:
>
>> But in any case, given what I did with the .marks files to take care
>> of my problem, I don't believe that we need anything besides that to
>> help people in their transitions through the recent versions of Oort.
>>
>> Or should there still be something else?
>
> FWIW, I didn't have to do anything at all. Just upgraded my Gnus.
Lloyd's analysis is correct, but he points a potential problem: If you
use a Gnus version with .mrk/.marks, then downgrade Gnus to a older
version and read alot of mail, and then upgrade Gnus again, you will
lose those marks added when you used the old Gnus. That is not nice.
But I wonder if up-down-up-grading isn't already considered harmful.
What happens if you downgrade Gnus, adds some articles to a nnfolder,
then upgrades to a Gnus that uses NOV nnfolders for instance? There
might be other examples as well. I remember many times when starting
old Emacsen and starting Gnus 5.3 (or something) which completely
destroyed my .newsrc.eld beyond repair.. (E.g the topics structure
was lost, I think.)
next prev parent reply other threads:[~2001-10-02 17:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-01 0:35 Lloyd Zusman
2001-10-01 6:09 ` Christoph Conrad
2001-10-01 20:53 ` Simon Josefsson
2001-10-01 22:00 ` Lloyd Zusman
2001-10-01 22:30 ` Lloyd Zusman
2001-10-02 11:43 ` Kai Großjohann
2001-10-02 11:53 ` Lloyd Zusman
2001-10-02 16:05 ` Kai Großjohann
2001-10-02 17:19 ` Simon Josefsson [this message]
2001-10-02 18:18 ` Dan Christensen
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=ilu8zeuc648.fsf@barbar.josefsson.org \
--to=jas@extundo.com \
--cc=ding@gnus.org \
--cc=ljz@asfast.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).