From: Carlos O'Donell <carlos@redhat.com>
To: Siddhesh Poyarekar <siddhesh@gotplt.org>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Cc: Joseph Myers <joseph@codesourcery.com>,
cti-tac@lists.linuxfoundation.org
Subject: Re: Next steps from GTI TAC meeting on 2023-03-08 - Evaluate cost of glibc migration.
Date: Thu, 25 May 2023 07:12:16 -0400 [thread overview]
Message-ID: <4ea74598-2ce4-804e-344c-c1465f9082c7@redhat.com> (raw)
In-Reply-To: <0f264640-83ca-18da-9b8f-e04e7e0fc960@gotplt.org>
On 5/24/23 17:12, Siddhesh Poyarekar wrote:
> On 2023-05-24 15:06, Konstantin Ryabitsev wrote:
>> On Wed, May 24, 2023 at 02:13:53PM -0400, Siddhesh Poyarekar wrote:
>>> It looks like the question of who to ultimately trust, either the gatekeeper
>>> committer (or two) who is the only person to have write access to the
>>> repository, or the admin who manages the box.
>>
>> The maintainer's action are in the public, while the admin's actions are
>> hidden.
>>
>>> The gatekeeper committer could also fabricate commits and push to the
>>> central repository in the same way.
>>
>> 1. Not with nearly as much impunity, especially if non-fast-forward pushes are
>> disallowed.
>
> If an admin makes a change that needs a fast-forward, anybody trying
> to sync their repos would see the forced update. I'll admit though
> that it's arguable how many would actually notice the message.
Right. Some of us would, and review the situation.
Let me be clear though, Google *accidentally* force pushed on glibc master branch
on 2023-01-10 and the hooks didn't stop them, and it is a known bug in our hooks.
Joseph noticed and called it out... I didn't notice. Nobody else noticed because
it was the most recent thing in HEAD and nobody had pulled yet.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2023-05-25 11:12 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-19 22:47 Next steps from GTI TAC meeting on 2023-03-08 - Evaluate cost of glibc migration Joseph Myers
2023-05-22 10:11 ` Joel Brobecker
2023-05-24 12:44 ` Carlos O'Donell
2023-05-24 13:43 ` Siddhesh Poyarekar
2023-05-24 14:12 ` Carlos O'Donell
2023-05-24 15:18 ` Siddhesh Poyarekar
2023-05-23 17:38 ` Konstantin Ryabitsev
2023-05-23 19:34 ` Joseph Myers
2023-05-23 19:52 ` Konstantin Ryabitsev
2023-05-23 20:12 ` Joseph Myers
2023-05-23 20:21 ` Konstantin Ryabitsev
2023-05-23 22:12 ` Joseph Myers
2023-05-24 16:29 ` Konstantin Ryabitsev
2023-05-24 18:13 ` Siddhesh Poyarekar
2023-05-24 18:55 ` Brian Behlendorf
2023-05-24 21:27 ` Siddhesh Poyarekar
2023-05-25 11:06 ` Carlos O'Donell
2023-05-24 19:06 ` Konstantin Ryabitsev
2023-05-24 19:42 ` Joseph Myers
2023-05-24 21:12 ` Siddhesh Poyarekar
2023-05-25 11:12 ` Carlos O'Donell [this message]
2023-05-24 18:58 ` Joseph Myers
2023-05-24 12:11 ` Siddhesh Poyarekar
2023-05-24 18:44 ` Joseph Myers
2023-05-24 19:58 ` Carlos O'Donell
2023-05-24 12:57 ` Carlos O'Donell
2023-05-24 18:46 ` Joseph Myers
2023-05-24 20:19 ` Carlos O'Donell
2023-05-24 20:48 ` Joseph Myers
-- strict thread matches above, loose matches on Subject: below --
2023-04-03 17:24 Carlos O'Donell
2023-04-12 20:46 ` Konstantin Ryabitsev
2023-04-12 21:28 ` Brian Behlendorf
2023-05-19 21:00 ` Konstantin Ryabitsev
2023-05-22 14:37 ` Ian Kelling
2023-05-24 20:50 ` Carlos O'Donell
2023-05-24 21:53 ` Ian Kelling
2023-05-25 11:02 ` 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=4ea74598-2ce4-804e-344c-c1465f9082c7@redhat.com \
--to=carlos@redhat.com \
--cc=cti-tac@lists.linuxfoundation.org \
--cc=joseph@codesourcery.com \
--cc=konstantin@linuxfoundation.org \
--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).