From: "Frank Ch. Eigler" <fche@redhat.com>
To: Carlos O'Donell <carlos@redhat.com>
Cc: cti-tac@lists.linuxfoundation.org
Subject: Re: Migration to CTI services should be an opportunity to reduce dependency on git hooks.
Date: Fri, 21 Jun 2024 09:30:48 -0400 [thread overview]
Message-ID: <20240621133048.GA24746@redhat.com> (raw)
In-Reply-To: <b3d04984-cec4-456f-a05d-7adccb1c3b3d@redhat.com>
Hi -
> The gcc community was locked out of committing because of
> issues with the AdaCore hooks: [...]
> My strong opinion, particularly for glibc is that we have as
> few hooks as possible, and timeout those remote hooks in a
> reasonable amount of time.
Note that these hooks exist only at the pleasure and control of each
individual project.
> As we transition the services we should be looking to architect
> a safe and robust system that can handle the hooks timing out [...]
You don't have to wait - such a thing can be prototyped today.
Is the issue mainly the lack of anyone's time to do that?
- FChE
next prev parent reply other threads:[~2024-06-21 13:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-21 12:42 Migration to CTI services should be an opportunity to reduce dependency on git hooks Carlos O'Donell
2024-06-21 13:30 ` Frank Ch. Eigler [this message]
2024-06-21 20:27 ` Carlos O'Donell
2024-07-08 15:59 ` Joseph Myers
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=20240621133048.GA24746@redhat.com \
--to=fche@redhat.com \
--cc=carlos@redhat.com \
--cc=cti-tac@lists.linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.