From: Glenn Morris <rgm@gnu.org>
To: emacs-devel@gnu.org
Subject: Re: Bugs against emacsbugs.donarmstrong.com
Date: Sat, 13 Dec 2008 18:33:30 -0500 [thread overview]
Message-ID: <ljbpvfr6ph.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <20081213231403.GR24493@volo.donarmstrong.com> (Don Armstrong's message of "Sat, 13 Dec 2008 15:14:03 -0800")
Don Armstrong wrote:
> Haven't looked at any of those, sorry.
If that means "haven't had time", that's OK. If it means "haven't seen
them", there's a problem, since you are registered as maintainer of
that package (?).
> [Basically, we'll send everything to one list, and then fork out the
> messages that only should go to bug-gnu-emacs to it, and vice versa
> for the control messages.
Presumably this means debbugs can't (easily) be changed internally to DTRT.
Couldn't you just use something@donarmstrong.com to receive all
debbugs output, then use procmail to send them on to bug-gnu-emacs or
emacs-bug-tracker? (Probably depends on the details of the forwarding
of bug-gnu-emacs to donarmstrong.com in the first place, of which I am
ignorant.)
> and 897.)
>
> This would require serious tracking of message-ids, which is kind of a PITA.
So my simple suggestion does not work?
If emacsbugs sees that bug-gnu-emacs or emacs-pretest-bug is already
Cc'd on a reply to bug, it should avoid sending out another copy to
the list. Ie, it treats it as a "quiet" submission only to be entered
in the tracker.
(Again, I suppose it might depend on how that forwarding works.)
And #430 (which you said was doable) might help a bit.
next prev parent reply other threads:[~2008-12-13 23:33 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-12 12:44 Bug tracker breaks rmail-next-same-subject Eli Zaretskii
2008-12-12 19:10 ` Stefan Monnier
2008-12-12 23:16 ` Eli Zaretskii
2008-12-12 21:47 ` Don Armstrong
2008-12-12 23:03 ` Eli Zaretskii
2008-12-12 23:25 ` Don Armstrong
2008-12-12 23:36 ` Eli Zaretskii
2008-12-12 23:57 ` Don Armstrong
2008-12-13 2:41 ` Eli Zaretskii
2008-12-13 9:42 ` Don Armstrong
2008-12-13 22:58 ` Glenn Morris
2008-12-13 23:14 ` Bugs against emacsbugs.donarmstrong.com Don Armstrong
2008-12-13 23:33 ` Glenn Morris [this message]
2008-12-14 0:23 ` Don Armstrong
2008-12-14 3:51 ` Stefan Monnier
2008-12-14 8:06 ` Stephen J. Turnbull
2008-12-14 10:13 ` Don Armstrong
2008-12-14 20:53 ` Glenn Morris
2008-12-14 21:27 ` Stefan Monnier
2008-12-17 5:39 ` Don Armstrong
2008-12-17 16:10 ` Stefan Monnier
2008-12-18 7:43 ` Don Armstrong
2008-12-18 21:46 ` Stefan Monnier
2008-12-14 8:14 ` Stephen J. Turnbull
2008-12-14 2:50 ` Stefan Monnier
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=ljbpvfr6ph.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--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).