From: "Frank Ch. Eigler" <fche@elastic.org>
To: owner@bugs.debian.org
Cc: Overseers mailing list <overseers@sourceware.org>,
"Frank Ch. Eigler" <fche@redhat.com>
Subject: Re: looping gcc/bugzilla <-> bugs.debian mail
Date: Sun, 22 Mar 2020 17:53:35 -0400 [thread overview]
Message-ID: <20200322215335.GC8709@elastic.org> (raw)
In-Reply-To: <20200322215024.pln3xbiu42277ww2@qor.donarmstrong.com>
Hi -
Another way to break the loop is to make clear which bug tracker
is the master, which is a replica. If sourceware/gcc's bugzilla
is the master upstream, then the debian one can RECEIVE updates
from it, but need not SEND (and especially RESEND) updates to it.
- FChE
next prev parent reply other threads:[~2020-03-22 21:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-17 13:33 Frank Ch. Eigler
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 [this message]
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=20200322215335.GC8709@elastic.org \
--to=fche@elastic.org \
--cc=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).