This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: GCC Git hooks


On Mon, 16 Sep 2019, Joel Brobecker wrote:
> 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.

>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.)

Gerald


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]