Re: [PATCH v2 00/12] Pulling signed/annotated tags

Junio C Hamano [off-list ref] writes:

Here is what I had in mind....

And then I changed my mind again. Using a single SP indent for multi-line
header fields make things easy to view.

| tree 20009beb1d5d0494347db5afbe80b364563dd511
| parent 8457d13895251ebf2f839ee6f74dd0087fb56334
| parent 6486ca6d77eaf4109b26b70da0b3a0158868e22f
| author Junio C Hamano [off-list ref] 1320781099 -0800
| committer Junio C Hamano [off-list ref] 1320781099 -0800
| mergetag object 6486ca6d77eaf4109b26b70da0b3a0158868e22f
|  type commit
|  tag test-tag
|  tagger Junio C Hamano [off-list ref] 1320471226 -0700
|  
|  test merge
|  -----BEGIN PGP SIGNATURE-----
|  Version: GnuPG v1.4.10 (GNU/Linux)
|  
|  iQIcBAABAgAGBQJOtMq7AAoJELC16IaWr+bLL30P/iEhPR+gkOpF09EshWZy7Vbu
|  ...
|  =eJX/
|  -----END PGP SIGNATURE-----
| 
| Merge tag 'test-tag' of ../git into HEAD
| 
| test merge

I am redoing the "signed-commit" series to also use this format.

The way I made the tag available to commit_tree() turned out to be a bit
too clever, by the way, and it would cause problems down the road when
these things need to be amended. Embedded "gpgsig" in a commit is about
the commit itself, and should not be carried over, but "mergetag" is about
the parent and should not be lost only because you wanted to fix a type
in your merge log message. I'll be redoing that part in the series and
hopefully the finished result would be ready for review after 1.7.8 final.