From: Don Armstrong <don@donarmstrong.com>
To: emacs-devel@gnu.org
Subject: Re: bug#25: Acknowledgement (frame parameter menu-bar-lines changes height of frame)
Date: Sun, 2 Mar 2008 15:06:40 -0800 [thread overview]
Message-ID: <20080302230640.GX2110@volo.donarmstrong.com> (raw)
In-Reply-To: <uve44izj8.fsf@gnu.org>
On Sun, 02 Mar 2008, Eli Zaretskii wrote:
> I'm confused: in another message you said to subscribe to
> emacsbugs.donarmstrong.com, but now you seem to be saying that the
> bug reports will be sent to recipients of bug-gnu-emacs? If the
> latter is correct, why should we subscribe to
> emacsbugs.donarmstrong.com?
emacsbugs@lists.donarmstrong.com is what the maintainer of the emacs
package is configured as, and the mailing list that receives all of
the mails that a maintainer would see. You should subscribe to it, if,
during this teseting period you want to see exactly the types of
messages that the maintainers would see.
When we actually deploy, my suggestion is that bug-gnu-emacs be
configured to send messages to submit@emacsbugs.gnu.org (or wherever
the debbugs install ends up) and current subscribers of the
bug-gnu-emacs list get stuck on a new mailing list where all bug
related e-mails are copied. [The equivalent for Debian is
debian-bugs-dist@lists.debian.org[1]] (An alternative equivalent would
be to keep the bug-gnu-emacs list, but have incomming mail not sent
from the debbugs install redirected to submit@emacsbugs.gnu.org.[2])
Each of the configured packages will presumably also have their own
mailing list which people can subscribe to if they aren't interested
in all emacs related bugs. [We also have hooks for EoC to allow for
subscription to single bugs if that's desired.]
Don Armstrong
1: This mailing list averages a few thousand messages a day.
2: I'm too used to smartlist which makes this sort of thing trivial;
no clue how to do it in mailman.
--
A citizen of America will cross the ocean to fight for democracy, but
won't cross the street to vote in a national election.
-- Bill Vaughan
http://www.donarmstrong.com http://rzlab.ucr.edu
prev parent reply other threads:[~2008-03-02 23:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <BDEIJAFNGDOAGCJIPKPBEEPECFAA.drew.adams@oracle.com>
[not found] ` <handler.25.B.12042761599705.ack@emacsbugs.donarmstrong.com>
2008-02-29 15:21 ` bug#25: Acknowledgement (frame parameter menu-bar-lines changes height of frame) Drew Adams
2008-02-29 15:45 ` Jason Rumney
2008-02-29 16:06 ` Drew Adams
2008-03-01 0:23 ` Don Armstrong
2008-03-01 0:02 ` Don Armstrong
2008-03-02 5:29 ` Stefan Monnier
2008-03-02 21:31 ` Eli Zaretskii
2008-03-02 23:06 ` Don Armstrong [this message]
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=20080302230640.GX2110@volo.donarmstrong.com \
--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).