unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Bill Wohler <wohler@newt.com>
To: emacs-devel@gnu.org
Subject: Re: How to reply to bug reports
Date: Sat, 09 Aug 2008 10:45:55 -0700	[thread overview]
Message-ID: <87sktersj0.fsf@olgas.newt.com> (raw)
In-Reply-To: 20080808182759.GH15867@volo.donarmstrong.com

Don Armstrong <don@donarmstrong.com> writes:

> On Fri, 08 Aug 2008, Stefan Monnier wrote:
>> > Can someone please tell me how to reply correctly to a bug report.
>> 
>> > If I do not cc bug-gnu-emacs, my reply won't appear there and chances to
>> > get feedback from other developers are low as I noticed a couple of
>> > times.  If I do cc bug-gnu-emacs I apparently file a new bug report as
>> > already happened twice this week.
>> 
>> 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.

I agree with Stefan. The submitter and others who participated should
always be cc'd. All other systems I'm on do so, so not doing so
violates the principle of least surprise. As a submitter, I like to
see the machinations since it shows that at least my report is getting
attention. Best of all is the email you get when the report is closed.

Not only that, most "machinations" are requests for additional
information from the OP or to ask them to test the CVS version.
Forcing the maintainer to go back to the archives to find the OP's
address is unnecessary work.

Please consider fixing this behavior. Thanks.

-- 
Bill Wohler <wohler@newt.com>  http://www.newt.com/wohler/  GnuPG ID:610BD9AD





  parent reply	other threads:[~2008-08-09 17:45 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
2008-08-09 17:45     ` Bill Wohler [this message]
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=87sktersj0.fsf@olgas.newt.com \
    --to=wohler@newt.com \
    --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).