From: "Jakub Narębski" <jnareb@gmail.com>
To: Junio C Hamano <gitster@pobox.com>,
Michael J Gruber <git@drmicha.warpmail.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/2] Documentation/technical: signature formats
Date: Sat, 25 Oct 2014 10:30:25 +0200 [thread overview]
Message-ID: <544B5FA1.2050804@gmail.com> (raw)
In-Reply-To: <xmqq7fzshqrb.fsf@gitster.dls.corp.google.com>
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?
--
Jakub Narębski
next prev parent reply other threads:[~2014-10-25 19:53 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 [this message]
2014-10-30 10:19 ` Michael J Gruber
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=544B5FA1.2050804@gmail.com \
--to=jnareb@gmail.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).