all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jason Rumney <jasonr@gnu.org>
To: Joe Wells <jbw@macs.hw.ac.uk>
Cc: bug-gnu-emacs@gnu.org, rms@gnu.org, drew.adams@oracle.com,
	emacs-devel@gnu.org
Subject: Re: which bug messages should be sent where?
Date: Wed, 11 Jun 2008 22:42:36 +0100	[thread overview]
Message-ID: <485046CC.8090805@gnu.org> (raw)
In-Reply-To: <86skvjeqdf.fsf_-_@macs.hw.ac.uk>

Joe Wells wrote:

> I believe the purpose of the bug-gnu-emacs mailing list should now be
> this:
>
>   The bug-gnu-emacs mailing list is (1) where people can send bug
>   reports and (2) where people who want to help can watch for bug
>   reports and the discussion of bug reports.

I agree, and the messages sent to bug-gnu-emacs should essentially be 
the same messages as before (ie no control messages, and done messages 
should be the raw message as the developer sent it, not prepended with 
standard messages and the original bug report.

The way I think the mail forwarding should work is this:


bug-gnu-emacs incoming mail address + numbered addresses for existing bugs
            |
            V
      bug tracker
            |
            V
bug-gnu-emacs mailing list and newsgroup


emacs-pretest-bug incoming mail address + numbered addresses for 
existing bugs
            |
            V
      bug tracker
            |
            V
  emacs-devel mailing list

control email address
       |
       V
   bug tracker
       |
       V
emacs-bug-tracker mailing list
(could also receive all the above messages)

The way it currently seems to work is:

bug-gnu-emacs incoming mail address
        |             |
        V             |
   bug tracker        |
        |             |
        V             V
bug-gnu-emacs mailing list and newsgroup


emacs-pretest-bug incoming mail address
        |             |
        V             |
   bug tracker        V
        |        emacs-devel mailing list
        V           
bug-gnu-emacs mailing list and newsgroup

control incoming mail address + numbered addresses for existing bugs
        |
        V
    bug tracker
        |
        V
bug-gnu-emacs mailing list and newsgroup


Which give us duplicates on the lists, and results in pretest bugs and 
control messages going out to the general bug list.





  reply	other threads:[~2008-06-11 21:42 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-10 19:02 bug#21: Scrolling occasionally stops in *compilation* Stefan Monnier
2008-06-10 19:47 ` Drew Adams
2008-06-10 19:47 ` Drew Adams
     [not found] ` <mailman.13010.1213128432.18990.bug-gnu-emacs@gnu.org>
2008-06-11 10:23   ` Joe Wells
2008-06-11 13:28     ` Drew Adams
2008-06-11 18:36       ` Don Armstrong
2008-06-11 17:45     ` Richard M Stallman
2008-06-11 18:50       ` Don Armstrong
2008-06-11 18:57         ` Stefan Monnier
2008-06-11 18:50       ` Don Armstrong
2008-06-11 19:14       ` which bug messages should be sent where? (was: Scrolling occasionally stops in *compilation*) Joe Wells
2008-06-11 21:42         ` Jason Rumney [this message]
2008-06-11 23:48           ` which bug messages should be sent where? Don Armstrong
2008-06-15 17:55         ` bug#388: which bug messages should be sent where? (was: Scrolling occasionally stops in *compilation*) Richard M Stallman
2010-03-17 16:12 ` bug#21: Scrolling occasionally stops in *compilation* Glenn Morris

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=485046CC.8090805@gnu.org \
    --to=jasonr@gnu.org \
    --cc=bug-gnu-emacs@gnu.org \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=jbw@macs.hw.ac.uk \
    --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.