From: prj@po.cwru.edu (Paul Jarc)
Subject: Re: Marks woes on upgrade from oort 0.03 -> 0.04.
Date: Sat, 12 Jan 2002 23:05:57 -0500 [thread overview]
Message-ID: <m3u1tq28uc.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <87y9j32jik.fsf@cs.utah.edu> (Karra's message of "Sun, 13 Jan 2002 05:46:52 +0530")
Karra <karra@cs.utah.edu> wrote:
> How about inserting the following into the manual?
>
> --- gnus.texi.old Sun Jan 13 05:36:43 2002
> +++ gnus.texi Sun Jan 13 05:42:19 2002
> @@ -13688,6 +13688,10 @@
> to restore the group (after restoring the backup into the nnml
> directory).
>
> +If for some reason you believe your @file{.marks} files are screwed
> +up, you can just delete them all. Gnus will then correctly regenerate
> +them next time it starts.
> +
Better also include a note that this will not necessarily always be
true in future versions. Right now, .newsrc.eld is storing a
redundant copy of the same information, but that may not always be the
case.
paul
next prev parent reply other threads:[~2002-01-13 4:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-03 11:13 Karra
2002-01-05 16:23 ` Lars Magne Ingebrigtsen
2002-01-13 0:16 ` Karra
2002-01-13 4:05 ` Paul Jarc [this message]
2002-01-19 22:10 ` 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=m3u1tq28uc.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
/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).