From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16668 invoked by alias); 17 Sep 2019 12:55:06 -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 16660 invoked by uid 89); 17 Sep 2019 12:55:06 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-8.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.1 spammy=msgid, 40sourcewareorg, UD:40sourceware.org, 40sourceware.org X-HELO: rock.gnat.com Received: from rock.gnat.com (HELO rock.gnat.com) (205.232.38.15) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 17 Sep 2019 12:55:04 +0000 Received: from localhost (localhost.localdomain [127.0.0.1]) by filtered-rock.gnat.com (Postfix) with ESMTP id F08E4117C32; Tue, 17 Sep 2019 08:55:02 -0400 (EDT) Received: from rock.gnat.com ([127.0.0.1]) by localhost (rock.gnat.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id cjhcfDbJ+aHK; Tue, 17 Sep 2019 08:55:02 -0400 (EDT) Received: from joel.gnat.com (localhost.localdomain [127.0.0.1]) by rock.gnat.com (Postfix) with ESMTP id A73AE117890; Tue, 17 Sep 2019 08:55:02 -0400 (EDT) Received: by joel.gnat.com (Postfix, from userid 1000) id B4D1382166; Tue, 17 Sep 2019 05:55:00 -0700 (PDT) Date: Tue, 17 Sep 2019 12:55:00 -0000 From: Joel Brobecker To: Gerald Pfeifer Cc: Joseph Myers , Jason Merrill , gcc@gcc.gnu.org, Maxim Kuvyrkov , Daniel Berlin Subject: Re: GCC Git hooks Message-ID: <20190917125500.GJ5263@adacore.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) X-SW-Source: 2019-09/txt/msg00119.txt.bz2 > > You mean the email notification sent by the hooks when a commit > > gets pushed? If yes, here is an example: > > > > https://www.sourceware.org/ml/gdb-cvs/2019-09/msg00041.html > > Thank you, Joel! I got a little worried how to best parse that ;-), > but then Joseph recommended against it and... > > On Mon, 16 Sep 2019, Joseph Myers wrote: > > Rather, I suggest using the emails only as a signal that something has > > been pushed to the repository. You can then e.g. use "git rev-parse HEAD" > > before and after updating the local checkout to see what the old and new > > HEAD commits were, and "git diff --name-only" to list the modified, new or > > removed files (as in the posted hook). > > ...luckily provided an alternative. Thanks for that, Joseph! I had > a look and have started to adjust my script following your recommendation. Not sure if the following could be of use, but the commit emails have some information in the email header itself. For instance, if you look at https://sourceware.org/cgi-bin/get-raw-msg?listname=gdb-cvs&date=2019-09&msgid=20190917115728.124469.qmail%40sourceware.org You can see: X-Act-Checkin: binutils-gdb X-Git-Author: Tom de Vries X-Git-Refname: refs/heads/gdb-8.3-branch X-Git-Oldrev: 6f4f8f476a4e41cc7117a8e85087963c0ac3e95b X-Git-Newrev: fafa92ec3ca92e06fdea8f0f6a0fb08f5f906f77 (the X-Act-Checkin field gives the name of the repository) > >From my perspective this should not hold off anything. I can keep > adjusting even once the switch has taken place and validate changes > manually during that period. > > When, roughly, do you expect the switch can be ready? I assume we'll > have some sort of flag day? (I got in contact with webmaster@gnu.org > who are asking the same questions.) Just for the avoidance of doubt, the only item on my list is to move the git-hooks' doc directly into the git-hooks repository so they can be easily found when going to the hooks' github page (in progress, pull request sent yesterday). -- Joel