From: Glenn Morris <rgm@gnu.org>
To: ding@gnus.org
Subject: gnus bug reports go to wrong address
Date: Fri, 01 Jul 2011 12:22:30 -0400 [thread overview]
Message-ID: <7woc1ekm2h.fsf@fencepost.gnu.org> (raw)
(I'm not subscribed to the list.)
All these bug reports:
8972, 8973, 8974, 8975
got assigned to the wrong debbugs package and hence sent to the wrong
mailing list, because the necessary debbugs header stuff was not placed
right at the start of the message body, where it needs to go.
If this is a Gnus problem, please fix it ASAP. Or make it crystal clear
to Gnus bug reporters what they need to do. Thanks.
I'll reassign the reports to the correct package, so any future mails to
these bugs will go to the right place, but you won't see the initial
reports on your bug mailing list.
next reply other threads:[~2011-07-01 16:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-01 16:22 Glenn Morris [this message]
2011-07-01 17:15 ` Ted Zlatanov
2011-07-01 17:22 ` Glenn Morris
2011-07-01 17:29 ` Ted Zlatanov
2011-07-01 17:32 ` Lars Magne Ingebrigtsen
2011-07-01 17:45 ` Glenn Morris
2011-07-01 19:02 ` Ted Zlatanov
2011-07-01 19:33 ` Glenn Morris
2011-07-01 19:37 ` Ted Zlatanov
2011-07-01 20:10 ` Glenn Morris
2011-07-02 1:10 ` Ted Zlatanov
2011-07-02 1:20 ` Glenn Morris
2011-07-02 1:38 ` Ted Zlatanov
2011-07-05 0:56 ` Dave Abrahams
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=7woc1ekm2h.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=ding@gnus.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).