public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Ted Ts'o" <tytso@mit.edu>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-ext4@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [GIT PULL] ext4 bugfixes for 3.2-rc5
Date: Tue, 20 Dec 2011 21:28:15 -0800	[thread overview]
Message-ID: <7vd3biijdc.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20111215190846.GA2709@thunk.org> (Ted Ts'o's message of "Thu, 15 Dec 2011 14:08:46 -0500")

Ted Ts'o <tytso@mit.edu> writes:

> Cool!  Does it save enough that GPG signature information can be
> verified later?  I'm a little fuzzy on what is covered by the
> signature which gets verified when you run the command "git verify-tag
> tytso-for-linus-20111214".  Better yet, does the new version of git
> have a command that will automatically verify the digital signature
> found in a merge commit?
>
> And this isn't in 1.7.8 yet, right?  I'd have to build version of git
> based on the next branch to play with this new signatury goodness?

The 'master' branch as of this week has the topic merged.



  parent reply	other threads:[~2011-12-21  5:28 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-14 19:20 [GIT PULL] ext4 bugfixes for 3.2-rc5 Theodore Ts'o
2011-12-15  2:50 ` Linus Torvalds
2011-12-15 19:08   ` Ted Ts'o
2011-12-15 22:13     ` Linus Torvalds
2011-12-21  5:28     ` Junio C Hamano [this message]
2011-12-21  5:37       ` Junio C Hamano
2011-12-21  5:41   ` Junio C Hamano
     [not found] <i82GC-j4-7@gated-at.bofh.it>
     [not found] ` <i89I5-3Bp-11@gated-at.bofh.it>
     [not found]   ` <i8oQP-4s2-29@gated-at.bofh.it>
     [not found]     ` <i8rOG-XY-7@gated-at.bofh.it>
2011-12-17  8:20       ` Nick Holloway

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=7vd3biijdc.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    /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