> 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 <[email protected]> 1405282495 -0700
>  committer Linus Torvalds <[email protected]> 1405282495 -0700
>  mergetag object bf40c92635d63fcc574c52649f7cda13e0418ac1
>   type commit
>   tag ext4_for_linus_stable
>   tagger Theodore Ts'o <[email protected]> 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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to