From: Joseph Myers <joseph@codesourcery.com>
To: Jeff Law <jeffreyalaw@gmail.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
Siddhesh Poyarekar <siddhesh@gotplt.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
Florian Weimer <fweimer@redhat.com>,
Carlos O'Donell via Libc-alpha <libc-alpha@sourceware.org>,
Carlos O'Donell <carlos@redhat.com>,
"Ryan S. Arnold" <ryan.arnold@gmail.com>,
Paul Eggert <eggert@cs.ucla.edu>,
Maxim Kuvyrkov <maxim.kuvyrkov@linaro.org>,
Andreas Schwab <schwab@suse.de>
Subject: Re: Core Toolchain Infrastructure - Services for glibc
Date: Thu, 20 Jul 2023 17:43:32 +0000 [thread overview]
Message-ID: <b0cfc0a9-73ae-a2ec-4ce7-6798d33d87d@codesourcery.com> (raw)
In-Reply-To: <cb51b83f-fda4-7a15-4ba2-5ce2aa0b51eb@gmail.com>
On Tue, 18 Jul 2023, Jeff Law via Libc-alpha wrote:
> BUt the key (I think) is they're not trybot/CI style hooks. They're doing
> things like wiring up commits to the lists/bugzilla, verifying ChangeLog bits
> and the like.
>
> I think the point is that any hooks need serious thought about what they do
> and the attack surface they represent. So for example firing off pre-commit
> CI, not advisable. Having a hook that queries another system for the state of
> pre-commit CI may be reasonable.
>
> I would think that verifying ChangeLog format might fall into the reasonable
> space. Not sure about lists/bz integration hooks.
Details of what the GCC hooks do / check are documented in the GCC service
enumeration.
https://lore.kernel.org/cti-tac/7e59d8db-7b26-1249-ad5c-67b7f3411e1@codesourcery.com/T/#u
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2023-07-20 17:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 21:58 Carlos O'Donell
2023-07-14 11:38 ` Florian Weimer
2023-07-14 15:34 ` Konstantin Ryabitsev
2023-07-18 11:47 ` Siddhesh Poyarekar
2023-07-18 12:26 ` Jakub Jelinek
2023-07-18 13:19 ` Jeff Law
2023-07-18 13:24 ` Siddhesh Poyarekar
2023-07-20 17:43 ` Joseph Myers [this message]
2023-07-18 13:38 ` Konstantin Ryabitsev
2023-08-03 10:10 ` Florian Weimer
2023-07-14 15:58 ` Mark Wielaard
2023-08-22 15:53 ` Frank Ch. Eigler
2023-08-23 7:57 ` Sourceware Infrastructure " Mark Wielaard
2023-08-29 20:45 ` Core Toolchain Infrastructure - " Carlos O'Donell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b0cfc0a9-73ae-a2ec-4ce7-6798d33d87d@codesourcery.com \
--to=joseph@codesourcery.com \
--cc=carlos@redhat.com \
--cc=eggert@cs.ucla.edu \
--cc=fweimer@redhat.com \
--cc=jakub@redhat.com \
--cc=jeffreyalaw@gmail.com \
--cc=konstantin@linuxfoundation.org \
--cc=libc-alpha@sourceware.org \
--cc=maxim.kuvyrkov@linaro.org \
--cc=ryan.arnold@gmail.com \
--cc=schwab@suse.de \
--cc=siddhesh@gotplt.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).