From: Junio C Hamano <gitster@pobox.com>
To: "Jakub Narębski" <jnareb@gmail.com>
Cc: Stefan Beller <sbeller@google.com>,
tom@oxix.org, Matthieu Moy <Matthieu.Moy@imag.fr>,
"git\@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [Request for Documentation] Differentiate signed (commits/tags/pushes)
Date: Mon, 06 Mar 2017 16:16:42 -0800 [thread overview]
Message-ID: <xmqqzigyx7o5.fsf@junio-linux.mtv.corp.google.com> (raw)
In-Reply-To: <47ad8b6d-0a65-2f8c-dcc5-49a8a8d5ab2a@gmail.com> ("Jakub Narębski"'s message of "Tue, 7 Mar 2017 00:59:10 +0100")
Jakub Narębski <jnareb@gmail.com> writes:
> Also from what I remember signed commits came before mergetags, that
> is the result of merging a signed tag (storing the signature of
> one of parents of the merge commit to not pollute tag namespace).
>
> And this workflow, from what I know, is quite useful.
The "commit -s" on a merge commit lets you as the integrator to
attest that you made that merge. The "mergetag" records the
signature by the contributor that says the tip that was merged was
what the contributor wanted to get merged.
It is entirely reasonable to sign a merge commit that merges a
signed tag. They serve two different and unrelated purposes.
next prev parent reply other threads:[~2017-03-07 0:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-06 19:59 [Request for Documentation] Differentiate signed (commits/tags/pushes) Stefan Beller
2017-03-06 22:13 ` Junio C Hamano
2017-03-06 22:52 ` Stefan Beller
2017-03-07 0:08 ` Junio C Hamano
2017-03-07 0:58 ` Stefan Beller
2017-03-06 23:03 ` Junio C Hamano
2017-03-06 23:59 ` Jakub Narębski
2017-03-07 0:16 ` Junio C Hamano [this message]
2017-03-07 7:16 ` Matthieu Moy
2017-03-07 9:23 ` Jeff King
2017-03-07 9:45 ` Tom Jones
2017-03-07 22:19 ` Stefan Beller
2017-03-08 5:41 ` Jeff King
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=xmqqzigyx7o5.fsf@junio-linux.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=Matthieu.Moy@imag.fr \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=sbeller@google.com \
--cc=tom@oxix.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.
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).