mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "George Spelvin" <linux@horizon.com>
To: linux@horizon.com, tytso@mit.edu
Cc: arnd@arndb.de, lftan@altera.com, linux@horizon.com,
	linux-kernel@vger.kernel.org, tglx@linutronix.de,
	torvalds@linux-foundation.org
Subject: Re: [GIT PULL] arch/nios2 for v3.19
Date: 9 Dec 2014 22:05:18 -0500	[thread overview]
Message-ID: <20141210030518.19336.qmail@ns.horizon.com> (raw)
In-Reply-To: <20141210015421.GB3370@thunk.org>

> Actually, git already preserves the signed annotated tag.  That's the
> only way git show --show-signature can verify the tag's gpg signature.
> 
> You can see original signed annotated tag via a command like this:
> 
> git cat-file -p 18b34d9a7a085ba8f9cafa6a0d002e2cbac87c1f

TIL, thank you!

For the others watching in, as you know all commits have "headers"
which are normally not printed.  The above commit looks like

>  tree 939755a58a68aae5e1241b2a905ea612aeb2e589
>  parent 502fde1a0a2990ec54eab5241d3135c545da7372
>  parent bf40c92635d63fcc574c52649f7cda13e0418ac1
>  author Linus Torvalds <torvalds@linux-foundation.org> 1405282495 -0700
>  committer Linus Torvalds <torvalds@linux-foundation.org> 1405282495 -0700
>  mergetag object bf40c92635d63fcc574c52649f7cda13e0418ac1
>   type commit
>   tag ext4_for_linus_stable
>   tagger Theodore Ts'o <tytso@mit.edu> 1405281748 -0400
>   
>   More bug fixes for ext4 -- most importantly, a fix for a bug
>   (introduced in 3.15) that can end up triggering a file system
>   corruption error after a journal replay.  (It shouldn't lead to any
>   actual data corruption, but it is scary and can force file systems to
>   be remounted read-only, etc.)
>   -----BEGIN PGP SIGNATURE-----

The "mergetag" header contains the original annotated tag, indented
by one space.

In this case, Ted included the same message (formatted slightly
differently) in the pull e-mail and Linus copied it into the
merge commit, so it worked out in the end.

  reply	other threads:[~2014-12-10  3:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-10  1:06 George Spelvin
2014-12-10  1:54 ` Theodore Ts'o
2014-12-10  3:05   ` George Spelvin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-12-09  8:36 Ley Foon Tan
2014-12-09  9:05 ` Arnd Bergmann
2014-12-09 20:52 ` Linus Torvalds
2014-12-09 22:49   ` Thomas Gleixner
2014-12-09 22:52     ` Linus Torvalds

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=20141210030518.19336.qmail@ns.horizon.com \
    --to=linux@horizon.com \
    --cc=arnd@arndb.de \
    --cc=lftan@altera.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    --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

all inboxes | Powered by JetHome®