From: Jason Rumney <jasonr@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: emacs-devel@gnu.org
Subject: Re: bug#25: Acknowledgement (frame parameter menu-bar-lines changes height of frame)
Date: Fri, 29 Feb 2008 15:45:17 +0000 [thread overview]
Message-ID: <47C8288D.3050406@gnu.org> (raw)
In-Reply-To: <003301c87ae6$b2175740$0600a8c0@us.oracle.com>
Drew Adams wrote:
> Uh, why are we getting such emails?
>
You are getting this because I picked one of your outstanding reports to
test the bug submission process. I didn't realise that it would result
in an auto-reply to you, next time I will forward an email from my own
address rather than resending an existing report with original headers
intact.
> And why does it say to submit further info about the bug to
> "25@emacsbugs.donarmstrong.com, as before." As before?
>
Obviously there are problems to be ironed out.
> We should continue to be able to sort mails by thread, sender, etc. in our mail
> clients, and not have a thread get split into different subjects, addresses,
> etc.
>
I think we're going to have to put up with some breakage of this ideal
while we make the transition to the new bug reporting system. Once the
new system is up and running, the prefixes on the subject line should be
consistent once the bug has hit the system. If we impose requirements
like "no changing the subject line" on bug reporting tools, we are going
to end up with a bug tracker that is basically an unsorted mailing list
archive that someone needs to go in and fix up by hand.
next prev parent reply other threads:[~2008-02-29 15:45 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BDEIJAFNGDOAGCJIPKPBEEPECFAA.drew.adams@oracle.com>
[not found] ` <handler.25.B.12042761599705.ack@emacsbugs.donarmstrong.com>
2008-02-29 15:21 ` bug#25: Acknowledgement (frame parameter menu-bar-lines changes height of frame) Drew Adams
2008-02-29 15:45 ` Jason Rumney [this message]
2008-02-29 16:06 ` Drew Adams
2008-03-01 0:23 ` Don Armstrong
2008-03-01 0:02 ` Don Armstrong
2008-03-02 5:29 ` Stefan Monnier
2008-03-02 21:31 ` Eli Zaretskii
2008-03-02 23:06 ` Don Armstrong
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=47C8288D.3050406@gnu.org \
--to=jasonr@gnu.org \
--cc=drew.adams@oracle.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 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).