From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from elastic.org (unknown [IPv6:2600:3c03::f03c:91ff:fe50:73f]) by sourceware.org (Postfix) with ESMTPS id 661A6385E000 for ; Sun, 22 Mar 2020 21:53:36 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 661A6385E000 Received: from vpn-home.elastic.org ([10.0.0.2] helo=elastic.org) by elastic.org with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92.3) (envelope-from ) id 1jG8XI-0004pa-2n; Sun, 22 Mar 2020 21:53:36 +0000 Received: from fche by elastic.org with local (Exim 4.92.3) (envelope-from ) id 1jG8XH-0003ZV-LX; Sun, 22 Mar 2020 17:53:35 -0400 Date: Sun, 22 Mar 2020 17:53:35 -0400 From: "Frank Ch. Eigler" To: owner@bugs.debian.org Cc: Overseers mailing list , "Frank Ch. Eigler" Subject: Re: looping gcc/bugzilla <-> bugs.debian mail Message-ID: <20200322215335.GC8709@elastic.org> References: <20200317133349.GB31451@redhat.com> <20200318200607.2hbqiktyah4kl2t4@qor.donarmstrong.com> <20200318212137.GA14365@cgf.cx> <20200322203829.y4tivs2zl63t43ir@qor.donarmstrong.com> <20200322204050.GB8709@elastic.org> <20200322215024.pln3xbiu42277ww2@qor.donarmstrong.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200322215024.pln3xbiu42277ww2@qor.donarmstrong.com> X-Sender-Verification: "" X-Spam-Status: No, score=-104.6 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, RCVD_IN_SBL_CSS, SPF_HELO_PASS, SPF_PASS, TXREP, USER_IN_WHITELIST autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: overseers@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Overseers mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Mar 2020 21:53:37 -0000 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