From: Sven Joachim <svenjoac@gmx.de>
To: Drew Adams <drew.adams@oracle.com>
Cc: 3938@emacsbugs.donarmstrong.com, Chong Yidong <cyd@stupidchicken.com>
Subject: bug#3938: BUG system seems messed up - I did not close this bug
Date: Tue, 28 Jul 2009 23:11:00 +0200 [thread overview]
Message-ID: <87d47kv7h7.fsf@turtle.gmx.de> (raw)
In-Reply-To: <FAA3752496454DD984A751046D9348D1@us.oracle.com> (Drew Adams's message of "Tue, 28 Jul 2009 13:47:26 -0700")
On 2009-07-28 22:47 +0200, Drew Adams wrote:
> There is a problem with the bug system, it seems. I sent a simple reply to
> Yidong's message, which had the original bug subject:
> bug#3938: 23.0.96; regression: minibuffer-message interferes with C-u
>
> However, somehow my reply got interpreted as CLOSING the bug. Yidong had closed
> it.
Yes, he had sent a message to 3938-done@e.d.b. _and_ to you. If you
reply to that, you need to edit out the "-done" part to prevent
re-closing the bug if you reopened it.
Since this is somewhat confusing, maybe it would be better to only send
bug closing messages to the nnnn-done address and not to the submitter
as well?
Sven
next prev parent reply other threads:[~2009-07-28 21:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <877hxsolnt.fsf@stupidchicken.com>
2009-07-26 23:30 ` bug#3938: 23.0.96; regression: minibuffer-message interferes with C-u Drew Adams
2009-07-28 15:55 ` bug#3938: marked as done (23.0.96; regression: minibuffer-message interferes with C-u) Emacs bug Tracking System
2009-07-28 20:20 ` Emacs bug Tracking System
[not found] ` <handler.3938.D3938.12488120693237.notifdone@emacsbugs.donarmstrong.com>
2009-07-28 20:47 ` bug#3938: BUG system seems messed up - I did not close this bug Drew Adams
2009-07-28 21:11 ` Sven Joachim [this message]
2009-07-28 21:59 ` Drew Adams
2009-07-29 15:43 ` Stefan Monnier
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=87d47kv7h7.fsf@turtle.gmx.de \
--to=svenjoac@gmx.de \
--cc=3938@emacsbugs.donarmstrong.com \
--cc=cyd@stupidchicken.com \
--cc=drew.adams@oracle.com \
/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).