From: Michael J Gruber <git@drmicha.warpmail.net>
To: "Jakub Narębski" <jnareb@gmail.com>,
"Junio C Hamano" <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/2] Documentation/technical: signature formats
Date: Thu, 30 Oct 2014 11:19:18 +0100 [thread overview]
Message-ID: <545210A6.5020302@drmicha.warpmail.net> (raw)
In-Reply-To: <544B5FA1.2050804@gmail.com>
Jakub Narębski schrieb am 25.10.2014 um 10:30:
> W dniu 2014-10-22 21:02, Junio C Hamano pisze:
>
>> A mergetag is not fundamentally a "signature" in the above sense,
>> though. It is just a dump of the object content in a regular object
>> header field (hence indented by one SP), and its contents having PGP
>> SIGNATURE is merely a natural consequence of the object recorded
>> being a signed tag. So the description of it in the same place as
>> description for signed tags and signed commits feels a little bit
>> out of place, but I do not think of a better place to describe it.
>
> Does this mean that you can merge annotated (but not signed) tag,
> and have it (as description of merged branch) in 'mergetag' header?
We don't do that (so far).
In principle we could do that, of course. (But I really wish mergetag
would point to the tag object rather than embed it.)
But the point of the merge tag is to "bake into the commit object" some
verifiable information about the source of the merge, or rather about
some of its parents.
Just adding some non-verifiable, "come-and-go" information seems to be
more suited for notes.
Michael
next prev parent reply other threads:[~2014-10-30 10:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 15:16 [PATCH 0/2] document signature formats Michael J Gruber
2014-10-22 15:16 ` [PATCH 1/2] Documentation/technical: " Michael J Gruber
2014-10-22 16:57 ` Jakub Narębski
2014-10-22 19:02 ` Junio C Hamano
2014-10-24 15:36 ` Michael J Gruber
2014-10-24 17:10 ` Junio C Hamano
2014-10-25 8:30 ` Jakub Narębski
2014-10-30 10:19 ` Michael J Gruber [this message]
2014-10-22 15:16 ` [PATCH 2/2] Documentation/technical: document push certificate format Michael J Gruber
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=545210A6.5020302@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.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).