From: "Drew Adams" <drew.adams@oracle.com>
To: "'Stephen J. Turnbull'" <stephen@xemacs.org>
Cc: 'Stefan Monnier' <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: RE: bug tracker woes/misunderstanding
Date: Fri, 13 May 2011 10:32:01 -0700 [thread overview]
Message-ID: <DA23CE6B99794CEBB6D45A821BAF3760@us.oracle.com> (raw)
In-Reply-To: <87pqnmcyld.fsf@uwakimon.sk.tsukuba.ac.jp>
> > Thanks, but I do not understand how what I did in this case differs
> > from what I always do, except for changing "RE" to "OT".
>
> "The doctor says, 'If it hurts when you do that, stop doing it.'"
My question was what was being done that caused this hurt. Was it just using
"OT"? Using "OT" in place of "RE"? Position of "OT/RE" within the Subject?
Something else?
> Explanation:
> Looking at the subject is heuristic. Typically the rule is: the bug
> number must be the first thing in the subject in exactly the same
> format as the tracker produces, except for "RE:" stripping. "OT" not
> a bug number, so the tracker assumes it's new bug.
Great. Please add your explanation as doc, wherever the bug tracker is
documented (assuming this info is not already there).
> > I just hit `Reply All', as usual. Looking at past replies of mine,
> > I see that some of the mails I replied to were addressed to
> > bug-gnu-emacs@gnu.org, and others were addressed to
> > <bugnb>@debbugs.gnu.org - and this within the same thread! Why?
>
> Why not? It works fine as long as you don't try to be smart with the
> subject line.
Undocumented (?). What is "being smart"? What should users avoid wrt changes
to the Subject line and other fields? Apparently (?) one should not remove "RE"
from the beginning of the line (or even move it to the right, from the
beginning?). Please document just what one should not do - IOW, define "being
smart".
> Some heuristic is necessary because copies of bug
> messages with the generic To: address are always going to exist, and
> people *will* reply to those.
No argument with why things are implemented the way they are. The question is
from a user point of view: what to do/not do. That implementation sounds
fragile to me, but I'm not trying to reimplement or redesign it. I'm just
trying to understand how to use it. You've heard of users, right?
> > but `Reply All' to both kinds seems to work.
>
> <bugnb>@ works by protocol (and is reliable). bug-gnu-emacs@ works by
> heuristic (don't push your luck!)
Users will use `Reply' and `Reply All'. Please document what changes to the
Subject line or other fields are no-no's.
next prev parent reply other threads:[~2011-05-13 17:32 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 [this message]
2011-05-13 17:37 ` Eli Zaretskii
2011-05-13 18:02 ` Drew Adams
2011-05-13 18:40 ` Eli Zaretskii
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=DA23CE6B99794CEBB6D45A821BAF3760@us.oracle.com \
--to=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).