From: "Soni L." <fakedme+git@gmail.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Cross-signing commits
Date: Fri, 5 Mar 2021 18:53:14 -0300 [thread overview]
Message-ID: <537258e7-fcf4-814c-c7c1-95c8d525f34a@gmail.com> (raw)
In-Reply-To: <YEKmVWHJchUhxZmn@camp.crustytoothpaste.net>
On 2021-03-05 6:44 p.m., brian m. carlson wrote:
> On 2021-03-05 at 16:47:14, Soni L. wrote:
> > We have a somewhat unusual use-case where we need to cross-sign commits. Is
> > there any way to do this in git? As far as one can tell, attempting to
> > cross-sign a commit would cause its hash to change, and creating a signed
> > child commit would break fast-forward merges. So these are a no-go.
>
> Can you explain what you mean by "cross-signing"? Are you proposing a
> situation where two parties sign the same commit?
Yep. See, the repos enforce signing, but they can also be forks. If
someone wants to track upstream in one of their branches they just
can't. Would be cool if they could just say they trust the commits by
signing the relevant commits with their own key instead - on the
assumption that they actually reviewed said commits.
next prev parent reply other threads:[~2021-03-05 21:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-05 16:47 Cross-signing commits Soni L.
2021-03-05 21:44 ` brian m. carlson
2021-03-05 21:53 ` Soni L. [this message]
2021-03-05 21:58 ` brian m. carlson
2021-03-05 23:45 ` Randall S. Becker
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=537258e7-fcf4-814c-c7c1-95c8d525f34a@gmail.com \
--to=fakedme+git@gmail.com \
--cc=git@vger.kernel.org \
--cc=sandals@crustytoothpaste.net \
/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 NNTP newsgroup(s).