From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 47089 invoked by alias); 17 Jan 2020 16:37:59 -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 47081 invoked by uid 89); 17 Jan 2020 16:37:59 -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=googlemail.com, googlemailcom, H*F:D*googlemail.com, UD:googlemail.com X-HELO: mail-wm1-f44.google.com Received: from mail-wm1-f44.google.com (HELO mail-wm1-f44.google.com) (209.85.128.44) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Fri, 17 Jan 2020 16:37:49 +0000 Received: by mail-wm1-f44.google.com with SMTP id a5so8090610wmb.0 for ; Fri, 17 Jan 2020 08:37:49 -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=rX8ESKKJTCy4g1PPHOgei3PHENLTKK+rBA4XxX7XxnA=; b=bvkcbWc+y362qyYfesKVSJCzDAZghM+Q9yexvSA4IQktvNqHmmbkadlRPTpv3v8avc 9opK052KRq+r5rVucgY6HRlY/rG9RWropfhddhCtuDJ7lGbG5a4kIP5jG2Zz33vtlqG0 d2wXGA2LZJdnsXUYFVDy9BSAJkIpJfpHWF4meo1nXQqp8+4I3xIARQvmAtBxdodP8JNH lnaZ9vXo6b0uyPjsS+Xyupdc1vl34cLs7QaVO6xkEqJbPTVY++EpXYGO4SYc40JN8++a qPmcCewpY4CJVpwzzcCOzO8nhZt3HATiJT5brn7X3Pr2sq6QpL9I7Ki+gfS3KSUJVOw1 5eIA== 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 d8sm35407775wre.13.2020.01.17.08.37.46 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 17 Jan 2020 08:37:46 -0800 (PST) Content-Type: text/plain; charset=utf-8; delsp=yes; format=flowed 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: <20200117154928.GB4164@adacore.com> Date: Fri, 17 Jan 2020 17:22:00 -0000 Cc: Joseph Myers , Jakub Jelinek , "Richard Earnshaw (lists)" , gcc@gcc.gnu.org Content-Transfer-Encoding: 8bit Message-Id: <05C5BE0B-911F-47B8-BB1C-56FE142422A8@googlemail.com> References: <20200115141617.GS10088@tucnak> <20200116114002.GB13162@adacore.com> <20200117154928.GB4164@adacore.com> To: Joel Brobecker X-SW-Source: 2020-01/txt/msg00341.txt.bz2 Joel Brobecker wrote: >> I think it's desirable for development that *happens on* the personal and >> vendor branches to be visible in gcc-cvs - that is different from things >> getting merged into them. >> >> Likewise for the refs/heads/devel/* development branches - >> non-fast-forward pushes are not permitted there, but such branches can >> expect to have lots of merges from master, and it's the actual development >> taking place *on* the branches - the new commits - that is of interest to >> see on gcc-cvs, not the merging of existing commits. > > Would it be sufficient to say that some branches would only > trigger a summary email, but not individual commit emails? > The downside is that you would not be getting the "diff" for > commits that are really completely new. But on the other hand, > it would fit better with the fact that user branches could have > frequent re-basing, thus causing the same commit email being sent > over and over at each rebase operation. It would also answer > the issue of the number of emails being sent when people are doing > a merge which brings in more commits than the max-emails number. AFAIU, we have access to more fine-grained information; isn’t it possible to differentiate “new” commits, from ‘merges’ and from ‘rebases’? (because a ‘new’ commit does not have the extra fields set up for merges and rebases). For example, I’d like to know that user/fred has rebased the branch i’m interested in but OTOH, would not find the per-commit mails useful (so a summary there is good). If a push contains a combination of things - new work, merged and rebased commits - then there would have to be some way to react to split or aggregate the messages / diffs per commit id. Iain