From: Junio C Hamano <gitster@pobox.com>
To: Tom Grennan <tmgrennan@gmail.com>
Cc: git@vger.kernel.org, jasampler@gmail.com, tomg.grennan@ericsson.com
Subject: Re: [RFC/PATCH] verify-tag: check sig of all tags to given object
Date: Fri, 03 Feb 2012 21:22:44 -0800 [thread overview]
Message-ID: <7vsjirjhp7.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20120204050818.GA2477@tgrennan-laptop> (Tom Grennan's message of "Fri, 3 Feb 2012 21:08:18 -0800")
Tom Grennan <tmgrennan@gmail.com> writes:
> Wouldn't you want Shawn and Jeff to tag the object (commit, tree, or
> blob) that you had tagged?
No.
We _designed_ our tag objects so that they are capable of pointing at
another tag, not the object that is pointed at that other tag. And that
is the example usage I gave you.
The statement by Shawn and Jeff, "This tag is Gitster's" is exactly that.
It was not about asserting the authenticity of the commit. It was about
the tag object I created.
> gitster$ git verify-tag --pointed v1.7.10
> tag v1.7.10: OK
Just saying "$name: OK" will *never* be acceptable. "A signature made by
any key in my keychain is fine" is not the usual use case. At least the
output needs to be "Good signature from X".
next prev parent reply other threads:[~2012-02-04 5:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-04 1:25 [RFC/PATCH] verify-tag: check sig of all tags to given object Tom Grennan
2012-02-04 3:16 ` Junio C Hamano
[not found] ` <D140688E-B86C-4A67-9AD6-56160C26884D@ericsson.com>
2012-02-04 5:08 ` Tom Grennan
2012-02-04 5:22 ` Junio C Hamano [this message]
2012-02-04 5:56 ` Tom Grennan
2012-02-04 6:20 ` Junio C Hamano
2012-02-04 6:49 ` Tom Grennan
2012-02-04 5:16 ` Junio C Hamano
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=7vsjirjhp7.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jasampler@gmail.com \
--cc=tmgrennan@gmail.com \
--cc=tomg.grennan@ericsson.com \
/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).