From: Rob Browning <rlb@cs.utexas.edu>
Subject: Re: Very unhappy (again). (Apologies)
Date: 21 Jan 2001 23:19:03 -0600 [thread overview]
Message-ID: <87k87otb94.fsf@raven.localnet> (raw)
In-Reply-To: <87r91wu17m.fsf@raven.localnet>
I'd like to apologize a bit for my tone, I definitely appreciate the
work the developers do, I was just a little stunned to find myself
again falling afoul of bad gnus karma :>
Regardless, I'd still like to report that 5.8.8 appears to lose the
unread state of messages that are "B r" respooled. I glanced at the
source, but it wasn't immediately obvious to me what the problem is.
Thanks.
--
Rob Browning <rlb@cs.utexas.edu> PGP=E80E0D04F521A094 532B97F5D64E3930
next prev parent reply other threads:[~2001-01-22 5:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-21 19:58 Very unhappy (again). What happened? "B r" marked all unread as read Rob Browning
2001-01-22 5:19 ` Rob Browning [this message]
2001-02-07 11:28 ` Kai Großjohann
2001-02-07 11:38 ` Paul Stevenson
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=87k87otb94.fsf@raven.localnet \
--to=rlb@cs.utexas.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).