From: Glenn Morris <rgm@gnu.org>
To: rms@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: Emacs pretest bug reports
Date: Tue, 06 Mar 2007 23:17:16 -0500 [thread overview]
Message-ID: <1nslchk7qr.fsf@fencepost.gnu.org> (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 wrote:
> There is a suggestion that we make emacs-pretest-bug an alias for
> emacs-devel. That means pretest bug reports will come here first.
I think that in principle there is some benefit to having a separate
emacs-pretest-bug, eg it makes it easy to see all bugs in one place
(in the absence of a bug tracker).
In practice, it's pretty broken, because:
i) some people report bugs to emacs-devel
ii) you in particular seem to like forwarding bug reports from
emacs-pretest-bug to emacs-devel, which potentially leads to
duplication of effort (eg when eedjits like me fail to notice this and
followup to the original bug report).
Would there be any use to messages that come from the
emacs-pretest-bug list being tagged (eg [emacs-pretest-bug]) in the
subject line? Again, I'm thinking of an easy way to see all bugs (and
again, it's broken by i) above).
Would you do this for gnu-emacs-bug too?
next prev parent reply other threads:[~2007-03-07 4:17 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
2007-03-07 4:17 ` Glenn Morris [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1nslchk7qr.fsf@fencepost.gnu.org \
--to=rgm@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.