From: Richard Stallman <rms@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [alinsoar@voila.fr: EVAL and mouse selection in *Completions*]
Date: Wed, 07 Mar 2007 12:26:13 -0500 [thread overview]
Message-ID: <E1HOzu1-0008Fj-B6@fencepost.gnu.org> (raw)
In-Reply-To: <6hodn5k7io.fsf@fencepost.gnu.org> (message from Glenn Morris on Tue, 06 Mar 2007 23:22:07 -0500)
Why do you forward bug reports from emacs-devel to emacs-devel, with
only the little "please DTRT and ACK" addition?
Because my experience is that this gets someone to debug and fix it.
If I don't do this, quite often nobody works on the bug.
It also gives me a reminder if nobody works on it.
It has the effect of
removing the OP from the CC list when people reply to your forward, as
well as creating a separate thread.
Perhaps I should reply instead.
next prev parent reply other threads:[~2007-03-07 17:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-05 21:50 [alinsoar@voila.fr: EVAL and mouse selection in *Completions*] Richard Stallman
2007-03-06 2:50 ` Glenn Morris
2007-03-06 3:12 ` Chong Yidong
2007-03-06 3:22 ` Nick Roberts
2007-03-06 3:57 ` Glenn Morris
2007-03-06 3:59 ` Glenn Morris
2007-03-06 9:10 ` martin rudalics
2007-03-06 14:45 ` Stefan Monnier
2007-03-07 4:35 ` Glenn Morris
2007-03-07 10:24 ` martin rudalics
2007-03-08 9:28 ` Glenn Morris
2007-03-06 22:36 ` Richard Stallman
2007-03-07 4:22 ` Glenn Morris
2007-03-07 17:26 ` Richard Stallman [this message]
2007-03-07 18:35 ` Stefan Monnier
2007-03-08 17:40 ` Richard Stallman
2007-03-08 19:07 ` Stefan Monnier
2007-03-09 21:27 ` Richard Stallman
-- strict thread matches above, loose matches on Subject: below --
2007-03-06 9:57 A Soare
2007-03-08 8:28 A Soare
2007-03-08 8:41 ` Nick Roberts
2007-03-08 21:47 ` Richard Stallman
2007-03-08 8:31 A Soare
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=E1HOzu1-0008Fj-B6@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rgm@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).