Git development
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Dave Jones <davej@redhat.com>, git@vger.kernel.org
Subject: Re: diff against a tag ?
Date: Thu, 28 Apr 2005 14:28:38 -0700	[thread overview]
Message-ID: <7vwtqm616h.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0504281358060.18901@ppc970.osdl.org> (Linus Torvalds's message of "Thu, 28 Apr 2005 14:01:40 -0700 (PDT)")

>>>>> "LT" == Linus Torvalds <torvalds@osdl.org> writes:

LT> Right now fsck is the only thing that reports tags that aren't referenced 
LT> some other way. Once you know the tag, things are easy - even without 
LT> Junio's patch you can just do
LT> 	object=$(cat-file tag $tag | sed 's/object //;q')
LT> and then you can just do
LT> 	diff-tree $object $(cat .git/HEAD)
LT> or whatever you want to do.

Of course you are right.  The patch is about skipping the first
step and requiring you to know what you have is a tag not a
commit.

LT> Dave: do a "fsck --tags" in your tree, and it will talk about the tags it
LT> finds. Then you can create files like .git/refs/tags/v2.6.12-rc2 that
LT> contain pointers to those tags..

Arrrrrrrrrgh!  I just did "fsck --tags" blindly X-<.  Good thing
I was not root.

Of course you meant "fsck-cache --tags" ;-).


  reply	other threads:[~2005-04-28 21:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-28 20:09 diff against a tag ? Dave Jones
2005-04-28 20:42 ` Junio C Hamano
2005-04-28 21:01   ` Linus Torvalds
2005-04-28 21:28     ` Junio C Hamano [this message]
2005-04-28 22:06     ` Dave Jones
2005-04-28 22:22       ` Linus Torvalds
2005-04-28 23:44         ` Dave Jones
2005-04-28 23:14     ` Morten Welinder
2005-04-28 23:27       ` 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=7vwtqm616h.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=davej@redhat.com \
    --cc=git@vger.kernel.org \
    --cc=torvalds@osdl.org \
    /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