From: Henrik Enberg <henrik@enberg.org>
Subject: Re: Exiting a group with (all?) expiring articles is currently broken
Date: Fri, 31 Aug 2001 20:01:26 +0200 [thread overview]
Message-ID: <m3bskwyuq1.fsf@enberg.org> (raw)
In-Reply-To: <vxkd75droz2.fsf@cinnamon.vanillaknot.com> (Karl Kleinpaste's message of "Thu, 30 Aug 2001 21:35:13 -0400")
Karl Kleinpaste <karl@charcoal.com> writes:
[...]
> The articles are not deleted, though enough internal updating has
> occurred that I can force exit with `Q' and find that the articles are
> considered to have been read. That is, the *Group* buffer shows `0'
> after exiting with `Q'.
I have roughly the same problem, I don't get any errors but when I exit
groups with expiry-target (and only those groups) set all remaining
articles gets marked as ancient (`O') instead of expirable (`E'). This
is probably somehow related to Andrew Innes changes on 2001-08-30, those
are atleast the only changes made between my last update where it did
work and now.
Henrik
--
Could I have a drug overdose?
next prev parent reply other threads:[~2001-08-31 18:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-31 1:35 Karl Kleinpaste
2001-08-31 18:01 ` Henrik Enberg [this message]
2001-08-31 19:04 ` Karl Kleinpaste
2001-08-31 19:15 ` Karl Kleinpaste
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=m3bskwyuq1.fsf@enberg.org \
--to=henrik@enberg.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).