all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Stephen J. Turnbull" <turnbull@sk.tsukuba.ac.jp>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 'Stefan Monnier' <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: RE: bug tracker woes/misunderstanding
Date: Sat, 14 May 2011 04:57:03 +0900	[thread overview]
Message-ID: <87k4ducr1s.fsf@uwakimon.sk.tsukuba.ac.jp> (raw)
In-Reply-To: <DA23CE6B99794CEBB6D45A821BAF3760@us.oracle.com>

Drew Adams writes:

 > Great.  Please add your explanation as doc, wherever the bug tracker is
 > documented (assuming this info is not already there).

Adding the explanation is a bad idea; it will encourage users to try
various "useful" changes as justified by their understanding of a
process accurately described only by its source code, and not promised
by the tracker maintainers.

 > I'm just trying to understand how to use it.

No, you're trying to go beyond "use".  Handling OT material in an
issue is *not* part of the job description of an issue tracker.
Issues are not the same as mailing list threads, and the appropriate
way for a user to present OT material is to find an appropriate new
channel, either a new issue or a different medium such as a mailing
list.

The feature of displaying a per-message subject could be useful (eg,
to announce availability of a patch or test case), but AFAICT it's
rarely used in debbugs (possibly because many other trackers don't
support it at all, they have a single subject for the whole issue).

 > Users will use `Reply' and `Reply All'.  Please document what changes to the
 > Subject line or other fields are no-no's.

All changes to header fields, except adding or removing addressees,
are forbidden to users of `Reply' and `Reply All'.

As Eli points out, the contents of admin/notes/bugtracker already say
what should be said.  Use the bug number address.  Everything else is
unsupported, although some effort is made to accomodate naive usage of
`Reply' (ie, simply typing a message body and sending, without mucking
with the headers).



      parent reply	other threads:[~2011-05-13 19:57 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
2011-05-13 19:24                 ` PJ Weisberg
2011-05-13 19:57         ` Stephen J. Turnbull [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k4ducr1s.fsf@uwakimon.sk.tsukuba.ac.jp \
    --to=turnbull@sk.tsukuba.ac.jp \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.