From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: stephen@xemacs.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: Re: bug tracker woes/misunderstanding
Date: Fri, 13 May 2011 21:40:01 +0300 [thread overview]
Message-ID: <83r582fnr2.fsf@gnu.org> (raw)
In-Reply-To: <206D2AC044E640119F6AAED2EE618F09@us.oracle.com>
> From: "Drew Adams" <drew.adams@oracle.com>
> Cc: <stephen@xemacs.org>, <monnier@iro.umontreal.ca>, <emacs-devel@gnu.org>
> Date: Fri, 13 May 2011 11:02:27 -0700
>
> > > Great. Please add your explanation as doc, wherever the
> > > bug tracker is documented (assuming this info is not already there).
> >
> > It is already there (admin/notes/bugtracker):
> >
> > ** How do I reply to an existing bug report?
> > Reply to 123@debbugs.gnu.org...
>
> Nope, but thanks for playing, Eli.
Why am I not surprised?
> That does not include the info from Stephen's explanation.
Yes, it does, if you read it carefully.
> 1. Users _will_ hit `Reply' and `Reply All'. And they will reply to direct
> replies to them from other users, i.e., mail that comes from other users and not
> from the bug tracker.
And that is okay. It works.
> It is not enough to tell users that they must always edit the recipient
> bug-gnu-emacs@gnu.org, replacing it with <bugnb>@debbugs.gnu.org. That is
> obviously not going to happen - including for users such as Eli Zaretskii.
> http://debbugs.gnu.org/cgi/bugreport.cgi?bug=8653#26
Users such as Eli Zaretskii know how to be careful about this. So
they are allowed some leeway. Users such as Drew Adams, who don't
always know what they are doing (or pretend they don't), should follow
the instructions to the letter.
> 2. Please add information about what kinds of editing of the Subject line are
> no-no's (at least in the case where the recipient is bug-gnu-emacs@gnu.org).
No edits are allowed, period.
next prev parent reply other threads:[~2011-05-13 18:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-13 14:30 bug tracker woes/misunderstanding Drew Adams
2011-05-13 14:58 ` Stefan Monnier
2011-05-13 15:18 ` Drew Adams
2011-05-13 16:02 ` Stefan Monnier
2011-05-13 16:06 ` Drew Adams
2011-05-13 16:43 ` Stefan Monnier
2011-05-13 16:54 ` Drew Adams
2011-05-13 18:19 ` Stefan Monnier
2011-05-13 18:25 ` Drew Adams
2011-05-13 17:14 ` Stephen J. Turnbull
2011-05-13 17:32 ` Drew Adams
2011-05-13 17:37 ` Eli Zaretskii
2011-05-13 18:02 ` Drew Adams
2011-05-13 18:40 ` Eli Zaretskii [this message]
2011-05-13 19:11 ` Drew Adams
2011-05-13 19:24 ` PJ Weisberg
2011-05-13 19:57 ` Stephen J. Turnbull
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=83r582fnr2.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=stephen@xemacs.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).