From: martin rudalics <rudalics@gmx.at>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Re: How to reply to bug reports
Date: Fri, 08 Aug 2008 22:50:46 +0200 [thread overview]
Message-ID: <489CB1A6.3010208@gmx.at> (raw)
In-Reply-To: <20080808182759.GH15867@volo.donarmstrong.com>
>> AFAIK, the only place you should need reply is to
>> NNN@emacsbugs.donarmstrong.com and that should go to all the right
>> places (i.e. to bug-gnu-emacs, to the OP, and hopefully to most other
>> people who participated in this bug report).
>
> It doesn't currently go to the submitter; the logic behind this is
> that the submitter doesn't always care about the machinations going
> about to fix the bug.
>
> However, the ability for a submitter to easily decide that they want
> to get information about a bug is something that I'm going to add;
> it's pretty high on my todo list. [It's part of the per-bug
> subscription setup that Debian already has, but hasn't been deployed
> for emacs bugs.]
I've been confused by a couple of things, especially by the fact that I
received a confirmation from the bug tracker almost _instantaneously_
but for at least two reports never received a copy via bug-gnu-emacs.
Either my mail provider (gmx) rejected them or the relay via
bug-gnu-emacs didn't work out. Only after Sven's explanation, and after
checking the archives, I found that my replies were indeed sent to
bug-gnu-emacs.
It would be probably more foolproof if the bug-tracker did explain in a
two or three lines how to reply correctly and where replies are sent to
(the original submitter, which list, any subscribers). Well, maybe this
is self-evident to everyone but me ...
Apart from that I do like the bug-tracker a lot. Sorry for the mess
I've been causing - someone will have to merge #671-#674 into #587 as
well as #657 into #466.
martin
next prev parent reply other threads:[~2008-08-08 20:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-08 11:52 How to reply to bug reports martin rudalics
2008-08-08 12:40 ` Sven Joachim
2008-08-08 13:11 ` martin rudalics
2008-08-08 13:25 ` Sven Joachim
2008-08-08 17:21 ` martin rudalics
2008-08-08 17:26 ` Stefan Monnier
2008-08-08 18:27 ` Don Armstrong
2008-08-08 18:51 ` Stefan Monnier
2008-08-08 20:50 ` martin rudalics [this message]
2008-08-09 17:45 ` Bill Wohler
2008-08-09 18:17 ` Don Armstrong
2008-08-12 19:05 ` Stefan Monnier
2008-08-12 20:01 ` Glenn Morris
2008-08-12 20:27 ` Stefan Monnier
2008-08-12 20:58 ` Glenn Morris
2008-08-13 20:38 ` Stefan Monnier
2008-08-17 3:29 ` Bill Wohler
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=489CB1A6.3010208@gmx.at \
--to=rudalics@gmx.at \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).