unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Glenn Morris <rgm@gnu.org>
To: Alan Mackenzie <acm@muc.de>
Cc: Michael Welsh Duggan <mwd@md5i.com>, 15784@debbugs.gnu.org
Subject: bug#15784: 24.3.50; cc-mode bug reporting
Date: Sun, 03 Nov 2013 19:31:36 -0500	[thread overview]
Message-ID: <jsvc09j9cn.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <20131103215429.GA2917@acm.acm> (Alan Mackenzie's message of "Sun, 3 Nov 2013 21:54:29 +0000")

Alan Mackenzie wrote:

>> It sends to bug-cc-mode@gnu.org.  It might make sense to change this to
>> send to the gnu debbugs list instead, with an appropriate cc-mode tag.
>
> Right at the moment, I don't think this would be a good idea.  CC Mode is
> also upstream from XEmacs, and bug reports come from that quarter, too.
> It is convenient to be able to filter a mailbox for mails addressed to
> *cc-mode*.  Mail to bug-gnu-emacs is much easier to lose in the sheer
> volume of postings.

I think you may have misunderstood the suggestion.
If you change c-submit-bug-report to send mail to
submit@debbugs.gnu.org, with an "X-Debbugs-Package: cc-mode" header,
then all those reports will still end up on the bug-cc-mode list, not
the bug-gnu-emacs list (ie, submit@debbugs will act like an alias for
bug-cc-mode). But they will get entered into the tracker and get bug
numbers. So this change would actually make it _less_ easier to lose
cc-mode bugs.

This is what Gnus does, for example, and they have the same XEmacs
issues as you do. It seems to be working fine for them.





  reply	other threads:[~2013-11-04  0:31 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-01 16:01 bug#15784: 24.3.50; cc-mode bug reporting Michael Welsh Duggan
2013-11-03 21:54 ` Alan Mackenzie
2013-11-04  0:31   ` Glenn Morris [this message]
2013-11-06 20:28     ` Alan Mackenzie
2013-11-06 20:52       ` Glenn Morris
2013-11-10 11:10       ` Alan Mackenzie
2013-11-10 18:43         ` Michael Welsh Duggan
2014-01-30  2:59           ` Glenn Morris
2015-05-27  6:31             ` 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

  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=jsvc09j9cn.fsf@fencepost.gnu.org \
    --to=rgm@gnu.org \
    --cc=15784@debbugs.gnu.org \
    --cc=acm@muc.de \
    --cc=mwd@md5i.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 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).