all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Don Armstrong'" <don@donarmstrong.com>, <emacs-devel@gnu.org>
Subject: RE: Subject of closure notifications sent to submitters [Re: bug#119acknowledged by developer (Closing fixed bugs)]
Date: Thu, 12 Jun 2008 09:48:21 -0700	[thread overview]
Message-ID: <008501c8ccac$1fffd400$c2b22382@us.oracle.com> (raw)
In-Reply-To: <20080612161126.GL15070@volo.donarmstrong.com>

> > Please add the original Subject to the Subject line. We shouldn't
> > have to open the mail and search its body to find what bug #119 is
> > (in this case, "modify-frame-parameters in Emacs 23 for fonts".
> > 
> > The status "acknowledged by developer (Closing fixed bugs)" 
> > is not needed in the
> > Subject line. What is needed is the original Subject.
> 
> No, what is needed in the subject line is an informative message which
> tells you why the bug has been closed. Using close with the control
> interface should not be done unless you've already sent a mail to the
> bug submitter explaining that their bug has been closed.
> 
> The subject contains the subject of the message that actually caused
> the bug to be closed, and explains what the message that it is sending
> you is about, which it did.

Well, what can I say? Such a subject line is useless to me. The only connection
it shows with the bug I filed is the bug number, and that is not the most
helpful for finding the thread of messages, including the original, that involve
the bug.

The status might be the most important thing to you, but to me, the most
important thing to see in the Subject line is, well, the original subject.

Guess we'll just have to agree to disagree about this one.

FWIW, any bug tracking system I've ever used sends mails that keep the original
bug title intact as the subject. Even when the original title does not
accurately describe the bug, it is kept (along with the bug number) as the bug
identifier, and that identifier is used in the Subject of all mails concerning
the bug.

Also, please at least add a link in the mail body to the original bug report in
a threaded list on a Web page. We should be able to just click a link in any
mail regarding a particular bug to get to the complete thread.





  reply	other threads:[~2008-06-12 16:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4850FC42.7060305@gnu.org>
2008-04-06  2:17 ` modify-frame-parameters in Emacs 23 for fonts Drew Adams
     [not found]   ` <handler.119.C.121326703431170.notifdonectrl.0@emacsbugs.donarmstrong.com>
2008-06-12 14:50     ` bug#119 acknowledged by developer (Closing fixed bugs) Drew Adams
2008-06-12 16:11       ` Subject of closure notifications sent to submitters [Re: bug#119 acknowledged by developer (Closing fixed bugs)] Don Armstrong
2008-06-12 16:48         ` Drew Adams [this message]
2008-06-12 17:27           ` Subject of closure notifications sent to submitters [Re: bug#119acknowledged " Don Armstrong
2008-06-12 18:24             ` Subject of closure notifications sent to submitters [Re:bug#119acknowledged " Drew Adams
2008-06-12 18:32               ` Don Armstrong
2009-01-01  2:20   ` bug#119: marked as done (modify-frame-parameters in Emacs 23 for fonts) Emacs bug Tracking System
2008-06-12 10:45 ` Processed: Closing fixed bugs Emacs bug Tracking System
     [not found] <495C2629.40504@gnu.org>
2008-12-13 19:02 ` bug#1562: 23.0.60; modify-frame-parameters in Emacs 23 for fonts Drew Adams
2008-12-13 20:46   ` Glenn Morris
2008-12-13 21:21     ` Drew Adams
2008-12-14 14:48   ` Jason Rumney
2008-12-14 17:30     ` Drew Adams
2009-01-01  2:20   ` bug#1562: marked as done (23.0.60; modify-frame-parameters in Emacs 23 for fonts) Emacs bug Tracking System

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='008501c8ccac$1fffd400$c2b22382@us.oracle.com' \
    --to=drew.adams@oracle.com \
    --cc=don@donarmstrong.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 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.