From: David Abrahams <dave@boost-consulting.com>
Subject: Bug report? (was: Scoring and `/ N')
Date: Mon, 14 Feb 2005 11:18:48 -0500 [thread overview]
Message-ID: <uhdkf868n.fsf@boost-consulting.com> (raw)
In-Reply-To: <ud5v8fngo.fsf@boost-consulting.com>
David Abrahams <dave@boost-consulting.com> writes:
> Hi,
>
> I have lowered the score on articles from me, so that I can bcc myself
> and recover discussion threads from my INBOX, but so that I don't
> normally have to look at my own message headers in the summary. But
> whenever I do `/ N' to get new articles, the ones I've sent since my
> last update appear in the summary. Is there a way to prevent it?
Since nobody seems to be able to answer this question, can someone
tell me who to report the bug to, and how to do it?
--
Dave Abrahams
Boost Consulting
www.boost-consulting.com
next prev parent reply other threads:[~2005-02-14 16:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-10 15:23 Scoring and `/ N' David Abrahams
2005-02-11 18:53 ` Jhair Tocancipa Triana
2005-02-11 18:17 ` David Abrahams
2005-02-14 16:18 ` David Abrahams [this message]
2005-02-15 20:44 ` Bug report? Reiner Steib
2005-02-16 14:43 ` David Abrahams
2005-02-15 22:02 ` Lawrence Mitchell
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=uhdkf868n.fsf@boost-consulting.com \
--to=dave@boost-consulting.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).