Re: git-tag bug? confusing git fast-export with double tag objects

From: Jeff King <peff@peff.net>
Date: May 19, 2009, 11:29 UTC
Message-ID: <20090519112914.GA21386@coredump.intra.peff.net>
In-Reply-To: <op.ut6ciwjl1e62zd@balu.cs.uni-paderborn.de>

On Tue, May 19, 2009 at 01:21:58PM +0200, Matthias Andree wrote:

> What else can we tag in Git? Commits and Tags.  Is it sensible and does it 
> work to tag blobs or trees?

A tagged blob:

  $ cd git && git show junio-gpg-pub | sed '/^--/Q'
  tag junio-gpg-pub
  Tagger: Junio C Hamano <junkio@cox.net>
  Date:   Tue Dec 13 16:33:29 2005 -0800

  GPG key to sign git.git archive.

  This blob object contains the GPG public key I use to sign git.git
  archive.

  To use it to verify tags I signed, do:

    $ git-cat-file blob junio-gpg-pub | gpg --import

  to import it into your keyring, and then

    $ git-verify-tag $tag_to_be_verified

A tagged tree:

  $ cd linux-2.6 && git show v2.6.11 | sed '/^--/Q'
  tag v2.6.11-tree

  This is the 2.6.11 tree object.

  NOTE! There's no commit for this, since it happened before I started with git.
  Eventually we'll import some sort of history, and that should tie this tree
  object up to a real commit. In the meantime, this acts as an anchor point for
  doing diffs etc under git.

-Peff