From: Junio C Hamano <gitster@pobox.com>
To: Jimit Bhalavat <jimit@rams.colostate.edu>
Cc: git@vger.kernel.org, David Huseby <dhuseby@linuxfoundation.org>
Subject: Re: GPG Commit Signing Project
Date: Tue, 07 Jul 2020 12:10:31 -0700 [thread overview]
Message-ID: <xmqq1rln5efs.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <3942AC4E-6798-442B-81E9-B3D9B10A4A56@rams.colostate.edu> (Jimit Bhalavat's message of "Tue, 7 Jul 2020 12:01:30 -0600")
Jimit Bhalavat <jimit@rams.colostate.edu> writes:
> When we last spoke, David Huseby, my mentor for Hyperledger Git
> Commit Signing Project, proposed an outline of what we are trying
> to achieve. We have come to the conclusion that me and him are
> going to spend the rest of the summer analyzing the format signing
> infrastructure and will have proposals and questions as we go.
I thought the conclusion was that there is nothing to do on the git
side as your project would wrap the non-GPG signing tool of your
choice to have an external interface that is similar to how GPG
looks to git and that has the added benefit that the product of your
project to interact with tools other than git [*1*]. So...
> I am also going to write a technical design document which will
> help us analyze the problem. I realize this is a larger long-term
> project that I think deserves a topic and how would I set a topic
> up?
... your longer-term plan may very well deserve a detailed technical
design document, but I am not sure what help our project can give
(other than obvious things like saying "good luck").
Sorry for not being able to help all that much.
[Reference]
*1* https://lore.kernel.org/git/xmqqd0642p3q.fsf@gitster.c.googlers.com/
next prev parent reply other threads:[~2020-07-07 19:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-07 18:01 GPG Commit Signing Project Jimit Bhalavat
2020-07-07 19:10 ` Junio C Hamano [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-08-18 18:43 Jimit Bhalavat
2020-08-18 20:32 ` Junio C Hamano
2020-08-19 10:19 ` brian m. carlson
2020-06-10 23:11 Jimit Bhalavat
2020-06-10 18:06 Jimit Bhalavat
2020-06-10 19:35 ` Junio C Hamano
2020-06-12 1:55 ` dwh
2020-06-12 2:24 ` brian m. carlson
2020-06-12 17:03 ` Junio C Hamano
2020-06-10 17:57 Jimit Bhalavat
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq1rln5efs.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--cc=dhuseby@linuxfoundation.org \
--cc=git@vger.kernel.org \
--cc=jimit@rams.colostate.edu \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).