From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 67511 invoked by alias); 15 Jan 2020 16:42:13 -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 67503 invoked by uid 89); 15 Jan 2020 16:42:13 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-5.9 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 spammy=folk, personal X-HELO: foss.arm.com Received: from foss.arm.com (HELO foss.arm.com) (217.140.110.172) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 15 Jan 2020 16:42:03 +0000 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id DC281328; Wed, 15 Jan 2020 08:42:01 -0800 (PST) Received: from e120077-lin.cambridge.arm.com (e120077-lin.cambridge.arm.com [10.2.78.81]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 1D7343F718; Wed, 15 Jan 2020 08:42:01 -0800 (PST) Subject: Re: gcc-cvs mails for personal/vendor branches for merge commits To: Joseph Myers , Jason Merrill Cc: Jakub Jelinek , gcc@gcc.gnu.org, Joel Brobecker References: <20200115141617.GS10088@tucnak> <014947f3-43a8-e54d-8798-5d5f104e1fbd@redhat.com> From: "Richard Earnshaw (lists)" Message-ID: <1ff2ca95-3a43-5ec6-a4b2-9b452d9aa088@arm.com> Date: Wed, 15 Jan 2020 19:21:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-SW-Source: 2020-01/txt/msg00315.txt.bz2 On 15/01/2020 16:30, 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. > How about separate email list(s) for the vendor and personal spaces? I do think changes there should be visible, but perhaps fewer folk will be interested in tracking them at the same level. R.