From: Lawrence Mitchell <wence@gmx.li>
Subject: Re: Bug report?
Date: Tue, 15 Feb 2005 22:02:26 +0000 [thread overview]
Message-ID: <?fnord?87wtt91nyl.fsf@ID-97657.usr.dfncis.de> (raw)
In-Reply-To: <uhdkf868n.fsf@boost-consulting.com>
David Abrahams wrote:
[...]
> 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?
M-x gnus-bug RET
--
Lawrence Mitchell <wence@gmx.li>
prev parent reply other threads:[~2005-02-15 22:02 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 ` Bug report? (was: Scoring and `/ N') David Abrahams
2005-02-15 20:44 ` Bug report? Reiner Steib
2005-02-16 14:43 ` David Abrahams
2005-02-15 22:02 ` Lawrence Mitchell [this message]
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='?fnord?87wtt91nyl.fsf@ID-97657.usr.dfncis.de' \
--to=wence@gmx.li \
/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).