From: Junio C Hamano <gitster@pobox.com>
To: Jimit Bhalavat <jimit@rams.colostate.edu>
Cc: git@vger.kernel.org
Subject: Re: GPG Commit Signing Project
Date: Wed, 10 Jun 2020 12:35:27 -0700 [thread overview]
Message-ID: <xmqq1rmmg1ds.fsf@gitster.c.googlers.com> (raw)
In-Reply-To: <E7E8DC8B-BB7D-42E1-BD0E-EF59775B9E75@rams.colostate.edu> (Jimit Bhalavat's message of "Wed, 10 Jun 2020 12:06:07 -0600")
Jimit Bhalavat <jimit@rams.colostate.edu> writes:
> I am Jimit Bhalavat, and I am a Junior at Colorado State
> University and my major is Computer Science. Recently, I accepted
> to work on Hyperledger Git Commit Signing Project through The
> Linux Foundation and my mentor is David Huseby. I am writing to
> you in order to ask you if you are the maintainer for the GPG
> Signing Project?
>
> Which branches are for refactoring/new features in the GPG Commit
> Signing Project?
The fact that I know almost nothing about "Hyperledger Git Commit
Signing Project" (other than the search term returns some hits from
the search engines [*1*]) makes me suspect that whatever branch I
control is not suitable to contribute to that project, which does
not have much to do with the Git project, where this mailing list is
its home for. Perhaps ask your mentor first?
[Reference]
*1* https://wiki.hyperledger.org/display/INTERN/Git+signing+with+DIDs
next prev parent reply other threads:[~2020-06-10 19:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-10 18:06 GPG Commit Signing Project Jimit Bhalavat
2020-06-10 19:35 ` Junio C Hamano [this message]
2020-06-12 1:55 ` dwh
2020-06-12 2:24 ` brian m. carlson
2020-06-12 17:03 ` Junio C Hamano
-- 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-07-07 18:01 Jimit Bhalavat
2020-07-07 19:10 ` Junio C Hamano
2020-06-10 23:11 Jimit Bhalavat
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=xmqq1rmmg1ds.fsf@gitster.c.googlers.com \
--to=gitster@pobox.com \
--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).