From: "Drew Adams" <drew.adams@oracle.com>
To: "'Francis Litterio'" <flitterio@gmail.com>, <emacs-devel@gnu.org>
Subject: RE: Please don't cross-post bug reports to emacs-devel
Date: Tue, 9 Sep 2008 13:35:30 -0700 [thread overview]
Message-ID: <000601c912bb$9a386020$0200a8c0@us.oracle.com> (raw)
In-Reply-To: <i5i6sks92lgq.fsf@gmail.com>
> > I see you figured out X-Debbugs-CC; but why are your issues all so
> > important that they should be discussed on two mailing lists?
>
> If there are two mailing lists, and they have identical subscriber
> lists, then there is no sense in posting to both lists. Of course, if
> the subscriber lists are identical, then why have two lists
> in the first place?
>
> You see where I'm going with this?
IMO, whether the subscriber lists are identical or not is irrelevant. I am
subscribed to both but want separate lists. Separate lists help a subscriber
more easily do different things with messages received from the different lists.
Lists should be defined based on their intended content.
However, I agree that there is little sense in ever posting (or replying) to
both emacs-devel and the Emacs bug list(s). (Regardless of whether their
subscribers are the same.) Pick the most appropriate list and post to that one.
Occasionally, a thread might be moved from one list to another, but there is
rarely a good reason to cross-post.
Count me out of any possible followups to this, BTW - it's fine with me if
others don't agree.
next prev parent reply other threads:[~2008-09-09 20:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-08 3:17 Please don't cross-post bug reports to emacs-devel Glenn Morris
2008-09-08 17:23 ` Francis Litterio
2008-09-09 18:39 ` Glenn Morris
2008-09-09 18:51 ` Francis Litterio
2008-09-09 20:35 ` Drew Adams [this message]
2008-09-09 20:42 ` 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='000601c912bb$9a386020$0200a8c0@us.oracle.com' \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=flitterio@gmail.com \
/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.