From: "Drew Adams" <drew.adams@oracle.com>
To: "'Eli Zaretskii'" <eliz@gnu.org>
Cc: stephen@xemacs.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org
Subject: RE: bug tracker woes/misunderstanding
Date: Fri, 13 May 2011 12:11:28 -0700 [thread overview]
Message-ID: <7B6F6F9D5C1E42679DBE377C63A807B7@us.oracle.com> (raw)
In-Reply-To: <83r582fnr2.fsf@gnu.org>
> > 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.
Really? I don't think so. Unless by "allowed" you mean something other than
"will work". Are you saying that _any_ editing of the Subject line will cause
the message not to be handled correctly?
If that is the case, then please say so in the help. Perhaps something like:
"This bug tracker is so fragile that if you edit the Subject
line at all then your message will not be handled correctly."
(Again, this is for the case where the recipient is bug-gnu-emacs@gnu.org.)
You might want to substitute something else for "fragile", if that is too
sensitive. "Mickey Mouse", perhaps?
> 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.
Then please add something about how the above is not really true, that advanced
users can carefully edit the Subject line. Perhaps something like this:
"Actually, this is true only for uninitiated users such as
Drew Adams, who don't know what they're doing. If you think
you can be careful about editing the Subject line and you
would like to know how and be allowed leeway to do so, then
please contact Eli Zaretskii."
next prev parent reply other threads:[~2011-05-13 19:11 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
2011-05-13 19:11 ` Drew Adams [this message]
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=7B6F6F9D5C1E42679DBE377C63A807B7@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--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).