> > 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 <tdevr...@suse.de> 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 webmas...@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
