unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard M Stallman <rms@gnu.org>
To: Don Armstrong <don@donarmstrong.com>
Cc: emacs-devel@gnu.org
Subject: Re: pretest, devel and bug lists
Date: Fri, 30 May 2008 09:32:34 -0400	[thread overview]
Message-ID: <E1K24ig-0001kt-3k@fencepost.gnu.org> (raw)
In-Reply-To: <20080529162250.GO15311@volo.donarmstrong.com> (message from Don Armstrong on Thu, 29 May 2008 17:22:50 +0100)

    > 2. Whether the bug tracker should send mail to bug-gnu-emacs.
    > 
    > That is the question I was talking about before. I think it should
    > NOT send any mail to bug-gnu-emacs, or to emacs-pretest-bug.

    The way bug-gnu-emacs works now, all of the messages which haven't
    come from the bug tracker get sent to the bug tracker first, which
    assigns new messages a bug number and modifies the headers
    accordingly. This first part can't really be changed and still have a
    functional bug tracker and a bug-gnu-emacs which works as it did
    previously.

I don't understand what that means, but I have a feeling you are not
talking about the same issue.  I am NOT talking about messages that
are actually sent to the list by users.  I am talking about the canned
messages that originate from the bug tracker.

    The only extraneous messages that the bug tracker sends (or at least,
    should be sending) to bug-gnu-emacs which wouldn't previously have
    been seen on that list are the control modification transcripts. 

Perhaps those are the messages I am talking about.

What I am saying is that it SHOULD NOT send those messages to
emacs-devel or bug-gnu-emacs.  Never.  It should send them to a
separate list, which people can subscribe to if they are interested.

I am not talking about any other question.




  reply	other threads:[~2008-05-30 13:32 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-27 20:20 pretest, devel and bug lists Glenn Morris
2008-05-27 20:33 ` Drew Adams
2008-05-27 21:23   ` Jason Rumney
2008-05-28 15:10     ` Richard M Stallman
2008-05-28 18:00       ` Stefan Monnier
2008-05-28 18:05         ` Sven Joachim
2008-05-28 19:48           ` Stefan Monnier
2008-05-28 18:30         ` David De La Harpe Golden
2008-05-28 18:44           ` Don Armstrong
2008-05-28 21:17         ` Nick Roberts
2008-05-29  0:12           ` Don Armstrong
2008-05-29 10:25           ` Richard M Stallman
2008-05-29 16:22             ` Don Armstrong
2008-05-30 13:32               ` Richard M Stallman [this message]
2008-05-30 16:32                 ` Don Armstrong
2008-05-30  3:52             ` Nick Roberts
2008-05-30 18:59               ` Stephen J. Turnbull
2008-05-31  2:07               ` Richard M Stallman
2008-05-27 22:41   ` Don Armstrong
2008-05-27 21:19 ` Chong Yidong
2008-05-27 22:01   ` Don Armstrong
2008-05-28  0:49 ` Stefan Monnier
2008-05-28  1:01   ` Karl Fogel
2008-05-28  1:52   ` Glenn Morris
2008-05-28  3:03     ` Stefan Monnier
2008-05-28  8:34   ` Stephen Berman
2008-05-28  9:45     ` Nick Roberts
2008-05-28 10:37       ` Stephen Berman
2008-05-28 12:41       ` Stefan Monnier
2008-05-28 21:30       ` David De La Harpe Golden
2008-05-28 12:40     ` Stefan Monnier
2008-05-28 22:03       ` Stephen Berman
2008-05-28 21:19   ` Reiner Steib

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=E1K24ig-0001kt-3k@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=don@donarmstrong.com \
    --cc=emacs-devel@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).