This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: glibc git commit hooks update.
- From: Florian Weimer <fweimer at redhat dot com>
- To: Joseph Myers <joseph at codesourcery dot com>
- Cc: Carlos O'Donell <codonell at redhat dot com>, libc-alpha <libc-alpha at sourceware dot org>, Mark Wielaard <mjw at redhat dot com>, Nick Clifton <nickc at redhat dot com>, Jeff Law <law at redhat dot com>, "Frank Ch. Eigler" <fche at redhat dot com>, Pedro Alves <palves at redhat dot com>
- Date: Thu, 16 May 2019 12:13:48 +0200
- Subject: Re: glibc git commit hooks update.
- References: <56d46408-8314-aa01-91da-f8e32f2f56d1@redhat.com> <alpine.DEB.2.21.1904172216090.14148@digraph.polyomino.org.uk> <ed822689-7171-b1de-ed46-bec81c9f266e@redhat.com> <alpine.DEB.2.21.1904181237590.30834@digraph.polyomino.org.uk> <87bm13wkes.fsf@oldenburg2.str.redhat.com> <alpine.DEB.2.21.1904181445270.5356@digraph.polyomino.org.uk>
* Joseph Myers:
> On Thu, 18 Apr 2019, Florian Weimer wrote:
>
>> Makes sense to me.
>>
>> I will try to raise the issue with the hook scripts maintainer. Is it
>> okay to leave the new hooks in place with the current behavior?
>
> Sure.
I believe this is now fixed. I installed a wrapper script that parses
the message that is about to be posted to Bugzilla, and skips calling
the actual script if it refers to a non-official branch. While this is
a bit hackish, it avoids changes to the generic hook scripts.
Thanks,
Florian