From: jidanni@jidanni.org
To: 8105@debbugs.gnu.org
Subject: bug#8105: make sure explanation comes along with control message
Date: Thu, 24 Feb 2011 10:47:40 +0800 [thread overview]
Message-ID: <871v2y87xv.fsf@jidanni.org> (raw)
Can you make it easier for developers to send some content along with their
#1463 acknowledged by developer (control message for bug 1462)
#1462 acknowledged by developer (control message for bug 1462)
#1465 acknowledged by developer (control message for bug 1462)
We just get lots of
'You should be hearing from them with a substantive response shortly,
in case you haven't already. If not, please contact them directly.'
Which didn't work either.
next reply other threads:[~2011-02-24 2:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <handler.8105.D8105.129851606020277.notifdone@debbugs.gnu.org>
2011-02-24 2:47 ` jidanni [this message]
2011-02-24 2:54 ` bug#8105: make sure explanation comes along with control message Glenn Morris
2011-02-24 3:22 ` bug#8105: closed (Re: make sure explanation comes along with control message) jidanni
2011-02-24 6:35 ` bug#8105: make sure submitter automatically gets reason jidanni
2011-02-24 18:44 ` Eli Zaretskii
2011-02-24 22:55 ` jidanni
2011-02-24 23:03 ` Don Armstrong
2011-02-24 23:12 ` jidanni
2011-02-25 8:25 ` bug#8105: add URL to the 'bug closed' message jidanni
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=871v2y87xv.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--cc=8105@debbugs.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).