From: Miles Bader <miles@gnu.org>
To: rms@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: Emacs pretest bug reports
Date: Wed, 07 Mar 2007 09:39:53 +0900 [thread overview]
Message-ID: <87odn5evja.fsf@catnip.gol.com> (raw)
In-Reply-To: <E1HOiGn-0000sX-3Q@fencepost.gnu.org> (Richard Stallman's message of "Tue\, 06 Mar 2007 17\:36\:33 -0500")
Richard Stallman <rms@gnu.org> writes:
> There is a suggestion that we make emacs-pretest-bug an alias for
> emacs-devel. That means pretest bug reports will come here first.
>
> Does anyone think this is a bad idea?
No; I think it's a good idea.
I'm subscribed to both, and have always thought it was suboptimal that
technical bug discussions which are clearly of interest to emacs-devel
readers (and which would benefit from their input) sometimes happen on
emacs-pretest-bug.
For existing emacs-devel readers, at least, it wouldn't be any burden,
because the traffic on emacs-pretest-bug is fairly light even right
before release. For emacs-pretest-bug readers, I suppose they might not
like the additional traffic of emacs-devel though.
-Miles
--
o The existentialist, not having a pillow, goes everywhere with the book by
Sullivan, _I am going to spit on your graves_.
next prev parent reply other threads:[~2007-03-07 0:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-06 22:36 Emacs pretest bug reports Richard Stallman
2007-03-06 22:59 ` Drew Adams
2007-03-06 23:27 ` Nick Roberts
2007-03-07 7:12 ` Jan Djärv
2007-03-07 10:31 ` Kim F. Storm
2007-03-07 0:39 ` Miles Bader [this message]
2007-03-07 4:17 ` Glenn Morris
2007-03-07 17:26 ` Richard Stallman
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=87odn5evja.fsf@catnip.gol.com \
--to=miles@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rms@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).