From: "serhei at serhei dot io" <sourceware-bugzilla@sourceware.org>
To: overseers@sourceware.org
Subject: [Bug Infrastructure/29615] prototype & document SOP for signed-git-op repo
Date: Mon, 26 Sep 2022 16:57:02 +0000 [thread overview]
Message-ID: <bug-29615-14326-St7UGTo3NZ@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-29615-14326@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=29615
Serhei Makarov <serhei at serhei dot io> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |serhei at serhei dot io
--- Comment #1 from Serhei Makarov <serhei at serhei dot io> ---
I'm open to putting the Bunsen repo through all the latest and most stringent
in git supply chain security best practices. Got to keep out those Ken Thompson
omniscient code gremlins.
We'll need to coordinate with Martin Cermak, as he's also pushing commits
directly to the repo. (Keith Seitz has also contributed, but he's always sent
patches to the mailing list for review so I assume he'll be ok with added steps
to the contribution procedure.)
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2022-09-26 16:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-26 13:30 [Bug Infrastructure/29615] New: " fche at redhat dot com
2022-09-26 16:57 ` serhei at serhei dot io [this message]
2022-09-26 17:20 ` [Bug Infrastructure/29615] " serhei at serhei dot io
2022-09-26 17:39 ` ezannoni at gmail dot com
2022-09-27 11:45 ` mark at klomp dot org
2022-09-27 13:23 ` serhei at serhei dot io
2022-09-27 20:10 ` mark at klomp dot org
2023-06-01 19:54 ` mark at klomp dot org
2023-10-14 1:02 ` fche at redhat dot com
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=bug-29615-14326-St7UGTo3NZ@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=overseers@sourceware.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).