From: Andrew Ardill <andrew.ardill@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Using signed tag in pull requests
Date: Wed, 18 Jan 2012 13:34:14 +1100 [thread overview]
Message-ID: <CAH5451mz7NpDyL9O708siBdgSC7eXZi=VWk5qd2Ghm0PmWZ9NQ@mail.gmail.com> (raw)
In-Reply-To: <7vwr8pok7w.fsf@alter.siamese.dyndns.org>
On 18 January 2012 12:47, Junio C Hamano <gitster@pobox.com> wrote:
> Andrew Ardill <andrew.ardill@gmail.com> writes:
>
>>> Starting from Git release v1.7.9, a contributor can add a signed tag to
>>> the commit at the tip of the history and ask the integrator to pull that
>>> signed tag. When the integrator runs `git pull`, the signed tag is
>>> automatically verified to assure that the history is not tampered with.
>>> In addition, the resulting merge commit records the content of the signed
>>> tag, so that other people can verify that the branch merged by the
>>> contributor was signed by the contributor, without fetching the signed tag
>>
>> I think you mean to say 'the branch merged by the integrator was signed
>> by the contributor'.
>
> Definitely. I'll update my local copy.
>
> Thanks for spotting this.
No worries. That's the whole point right? :D
prev parent reply other threads:[~2012-01-18 2:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-17 22:53 Using signed tag in pull requests Junio C Hamano
2012-01-17 23:29 ` [PATCH] pulling signed tag: add howto document Junio C Hamano
2012-01-18 15:15 ` Marc Branchaud
2012-01-18 21:22 ` Junio C Hamano
2012-01-18 21:40 ` Marc Branchaud
2012-01-18 22:27 ` Junio C Hamano
2012-01-18 22:35 ` Marc Branchaud
2012-01-18 1:07 ` Using signed tag in pull requests Andrew Ardill
2012-01-18 1:47 ` Junio C Hamano
2012-01-18 2:34 ` Andrew Ardill [this message]
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='CAH5451mz7NpDyL9O708siBdgSC7eXZi=VWk5qd2Ghm0PmWZ9NQ@mail.gmail.com' \
--to=andrew.ardill@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=linux-kernel@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).