From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 60103 invoked by alias); 15 Jan 2020 16:38:07 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 60018 invoked by uid 89); 15 Jan 2020 16:38:07 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-3.6 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=HX-Spam-Relays-External:209.85.221.68, H*RU:209.85.221.68, googlemail.com, googlemailcom X-HELO: mail-wr1-f68.google.com Received: from mail-wr1-f68.google.com (HELO mail-wr1-f68.google.com) (209.85.221.68) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 15 Jan 2020 16:37:54 +0000 Received: by mail-wr1-f68.google.com with SMTP id d16so16404701wre.10 for ; Wed, 15 Jan 2020 08:37:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=gZvtpDe5KeVvGT+tjCcKyhSRIF9/Ugjup1/ZbvppAj4=; b=UWERa9aLCiI9NcsQrK4a5olU8jq/G9yF7b0E6JC20vIVIEWRFDHqrOsPVWoU2f7wVx Qc0UPvC3pAcyKzqyysxOmPQZm6nkZmuDVByyiz8CN9FaA+LVzoakXlOorU/ECBHRs2gM 45MLghxRysEC3gKWOo9N4pmfuaSylmIGDLA4cY/d2F1PurT/3TDPSpvr1/gGANQ/lC2p EtECMYoCuh2z/H3VvLgBv4XE6xarnMGLowf4a7QxhKXByWHNo13gb4u7eCyLIonst6wJ j3mzuJ+aIWl+pkvcXWdLpw/r98HDT3daIjOSdhI4ShDcMNAGD2GAf8z/vXrticufZJ4R cuGA== Return-Path: Received: from [192.168.1.212] (host81-138-1-83.in-addr.btopenworld.com. [81.138.1.83]) by smtp.googlemail.com with ESMTPSA id n67sm464854wmf.46.2020.01.15.08.37.50 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 15 Jan 2020 08:37:51 -0800 (PST) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: Re: gcc-cvs mails for personal/vendor branches for merge commits From: Iain Sandoe In-Reply-To: Date: Wed, 15 Jan 2020 17:57:00 -0000 Cc: Jason Merrill , Jakub Jelinek , "Richard Earnshaw (lists)" , gcc@gcc.gnu.org, Joel Brobecker Content-Transfer-Encoding: 8bit Message-Id: <89C87961-B21A-4E54-914F-40A89B5D5BBD@googlemail.com> References: <20200115141617.GS10088@tucnak> <014947f3-43a8-e54d-8798-5d5f104e1fbd@redhat.com> To: Joseph Myers X-SW-Source: 2020-01/txt/msg00314.txt.bz2 Joseph Myers wrote: > On Wed, 15 Jan 2020, Jason Merrill wrote: > >> On 1/15/20 9:56 AM, Joseph Myers wrote: >>> On Wed, 15 Jan 2020, Jakub Jelinek wrote: >>> >>>> Or, if that is not possible, disable gcc-cvs mail for vendor and private >>>> branches altogether? >> >> I think this is desirable. gcc-cvs should only mail about changes to master >> and release branches. > > I thinks commit mails for changes to all branches are desirable (including > refs/heads/devel/ branches, including user and vendor branches) - but they > should only be for changes that are new to the repository. Existing > practice in SVN was that all branches generated mails, we simply didn't > have so many branches. For user/vendor branches that are rebased (a desirable action), is there any mechanism for excluding unchanged rebased commits from being seen as “new”? I’m guessing that public development branches will probably gravitate to the no non-FF mode, if they are to be used by people other than the primary author .. although that does somewhat limit things; rebasing WIP onto trunk and reorganising / squashing is useful as well. Iain