From: "Frank Ch. Eigler" <fche@redhat.com>
To: owner@bugs.debian.org
Cc: overseers@sourceware.org
Subject: looping gcc/bugzilla <-> bugs.debian mail
Date: Tue, 17 Mar 2020 09:33:49 -0400 [thread overview]
Message-ID: <20200317133349.GB31451@redhat.com> (raw)
Hi -
We have a mail loop situation happening between bugs.debian.org
and sourceware.org (= gcc.gnu.org)'s bugzilla servers. Can you
advise whether we should stop this somehow or whether you can
from your end?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3481
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=55298
Not sure what set off the two robots talking to each other,
but it wasn't entertaining the bystanders.
- FChE
next reply other threads:[~2020-03-17 13:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-17 13:33 Frank Ch. Eigler [this message]
2020-03-18 20:06 ` Don Armstrong
2020-03-18 21:21 ` Christopher Faylor
2020-03-22 20:38 ` Don Armstrong
2020-03-22 20:40 ` Frank Ch. Eigler
2020-03-22 21:50 ` Don Armstrong
2020-03-22 21:53 ` Frank Ch. Eigler
2020-03-18 22:37 ` Joseph Myers
2020-03-19 3:28 ` Christopher Faylor
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=20200317133349.GB31451@redhat.com \
--to=fche@redhat.com \
--cc=overseers@sourceware.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).