From: Colin Watson <cjwatson@debian.org>
To: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
Cc: Debian Bug Tracking System <owner@bugs.debian.org>, gcc@gcc.gnu.org
Subject: Re: Automatic reply by the debian bug tracking system spams GNATS and vice versa
Date: Sun, 05 Jan 2003 18:24:00 -0000 [thread overview]
Message-ID: <20030105182159.GB18362@riva.ucam.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0212181011530.16100-100000@gandalf.ticam.utexas.edu>
On Wed, Dec 18, 2002 at 10:18:04AM -0600, Wolfgang Bangerth wrote:
> Sometimes people file reports in the gcc bug tracking system GNATS which
> have already been reported to the Debian system. They then enter the
> latter system's address address into the CC-field of the GNATS report.
>
> Now when someone changes something at a report within GNATS, the change
> message also goes to the Debian system, which answers with an automatic
> receipt message. This receipt message is sometimes picked up by GNATS
> automatically as a new report, in which the submitter is the Debian
> system, and the Debian system also sometimes picks up the GNATS change
> message as a new report.
We have temporarily broken this loop by causing debbugs not to send acks
to gcc-gnats@gcc.gnu.org, but this isn't a very satisfactory solution.
Could a GNATS hacker please get in touch so that we can discuss
something more permanent (e.g. using the Precedence: header on both
sides)?
Thanks,
--
Colin Watson [cjwatson@flatline.org.uk]
prev parent reply other threads:[~2003-01-05 18:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <handler.x.Q85908.10402267865251.unknown@bugs.debian.org>
2002-12-18 9:01 ` Wolfgang Bangerth
2003-01-05 18:24 ` Colin Watson [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030105182159.GB18362@riva.ucam.org \
--to=cjwatson@debian.org \
--cc=bangerth@ticam.utexas.edu \
--cc=gcc@gcc.gnu.org \
--cc=owner@bugs.debian.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.
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).