From: "Drew Adams" <drew.adams@oracle.com>
To: <emacs-devel@gnu.org>
Subject: bug and dev mailing lists [was: bugfix eshell/rm]
Date: Sat, 12 Mar 2011 12:12:47 -0800 [thread overview]
Message-ID: <5A27109894BF4A56A72FEE8CAF886FA1@us.oracle.com> (raw)
In-Reply-To: <mxtyf8mbdh.fsf@fencepost.gnu.org>
> From: Glenn Morris
>
> We have separate mailing lists for a reason.
Amen. So why have some taken to cross-posting from the bugs list to the dev
list lately?
E.g. bug 8219. In this case it was Eli who cross-posted to emacs-devel, but I
think he's not the only one who has done this.
I'm all for moving a discussion to emacs-devel if that is appropriate. Or
creating a separate development discussion thread there. But cross-posting from
the bug list to the dev list should be a no-no, IMO.
Nothing prevents one from updating a bug thread with some conclusion or
occasional input from a related dev thread - or vice versa. But simply cc'ing
the other thread as a mirror is a bad idea.
next prev parent reply other threads:[~2011-03-12 20:12 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 8:04 bugfix eshell/rm Thierry Volpiatto
2011-03-11 8:16 ` Glenn Morris
2011-03-11 9:08 ` Thierry Volpiatto
2011-03-11 10:18 ` Eli Zaretskii
2011-03-11 12:17 ` Thierry Volpiatto
2011-03-11 12:23 ` Eli Zaretskii
2011-03-11 12:50 ` Thierry Volpiatto
2011-03-11 15:59 ` Eli Zaretskii
2011-03-11 18:03 ` Thierry Volpiatto
2011-03-12 18:39 ` Glenn Morris
2011-03-12 20:12 ` Drew Adams [this message]
2011-03-12 20:25 ` bug and dev mailing lists [was: bugfix eshell/rm] Eli Zaretskii
2011-03-12 22:43 ` Drew Adams
2011-03-12 8:30 ` bugfix eshell/rm Thierry Volpiatto
2011-03-12 8:45 ` Thierry Volpiatto
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=5A27109894BF4A56A72FEE8CAF886FA1@us.oracle.com \
--to=drew.adams@oracle.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).