From: Don Armstrong <don@donarmstrong.com>
To: emacs-devel@gnu.org
Subject: Re: which bug messages should be sent where?
Date: Wed, 11 Jun 2008 16:48:00 -0700 [thread overview]
Message-ID: <20080611234800.GF17024@archimedes.ucr.edu> (raw)
In-Reply-To: <485046CC.8090805@gnu.org>
On Wed, 11 Jun 2008, Jason Rumney wrote:
> 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.
I can swap these around for messages sent to the maintainer and
mailing list so the -done is first, and the original message is at the
end so the informative bit is the first thing that is seen.
> 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
This is how it actually works.
> emacs-pretest-bug incoming mail address + numbered addresses for
> existing bugs
> |
> V
> bug tracker
> |
> V
> emacs-devel mailing list
[I didn't set this up, so I'm not sure.]
Don Armstrong
--
No amount of force can control a free man, a man whose mind is free
[...] You can't conquer a free man; the most you can do is kill him.
-- Robert Heinlein _Revolt in 2010_ p54
http://www.donarmstrong.com http://rzlab.ucr.edu
next prev parent reply other threads:[~2008-06-11 23:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <jwvej75ru6o.fsf-monnier+emacsbugreports@gnu.org>
2008-06-10 19:47 ` bug#21: Scrolling occasionally stops in *compilation* 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 19:14 ` which bug messages should be sent where? (was: Scrolling occasionally stops in *compilation*) Joe Wells
2008-06-11 21:42 ` which bug messages should be sent where? Jason Rumney
2008-06-11 23:48 ` Don Armstrong [this message]
2008-06-15 17:55 ` bug#388: which bug messages should be sent where? (was: Scrolling occasionally stops in *compilation*) Richard M 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=20080611234800.GF17024@archimedes.ucr.edu \
--to=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).