From: Stephen & Linda Smith <ischis2@cox.net>
To: git@vger.kernel.org
Subject: Signed tags and git repository
Date: Wed, 25 Nov 2015 16:19:07 -0700 [thread overview]
Message-ID: <3816223.3lD8Al3iuQ@thunderbird> (raw)
I've been following commits to the linux and git repostitories for some time. I used signed tags for
projects that I'm working on.
I know that the linux and git repositories have signed tags, but I'm not able to verify
them because my key isn't signed by anyone that leads back to one of the git or linux
maintainers. Of course I live in a technical desert since there seems to be no one that I
can find who lives in Phoenix, AZ that has a relationship to one of those two
git repositories.
What have others done when they want their keys signed so they can be part of the
web of trust? Does either of those two projects have a formal way of establishing these
relationships?
sps
next reply other threads:[~2015-11-26 0:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 23:19 Stephen & Linda Smith [this message]
2015-11-26 3:56 ` Signed tags and git repository Johannes Löthberg
2015-11-26 5:07 ` Stephen & Linda Smith
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=3816223.3lD8Al3iuQ@thunderbird \
--to=ischis2@cox.net \
--cc=git@vger.kernel.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 NNTP newsgroup(s).