From: Dave Jones <davej@redhat.com>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: diff against a tag ?
Date: Thu, 28 Apr 2005 19:44:51 -0400 [thread overview]
Message-ID: <20050428234451.GB1730@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0504281518100.18901@ppc970.osdl.org>
On Thu, Apr 28, 2005 at 03:22:21PM -0700, Linus Torvalds wrote:
> > Hmm, in a fresh rsync from your kernel tree, I get this..
> > tagged commit a2755a80f40e5794ddc20e00f781af9d6320fafb (v2.6.12-rc3) in 0397236d43e48e821cce5bbe6a80a1a56bb7cc3a
> > tagged commit 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 (v2.6.12-rc2) in 9e734775f7c22d2f89943ad6c745571f1930105f
> > expect dangling commits - potential heads - due to lack of head information
> > dangling tag 0397236d43e48e821cce5bbe6a80a1a56bb7cc3a
> > dangling commit 9acf6597c533f3d5c991f730c6a1be296679018e
> > dangling tag 9e734775f7c22d2f89943ad6c745571f1930105f
> >
> > Is that last part to be expected ?
> It even says so: "expect dangling commits".
heh, I was hex-blinded.
> The tags will always be dangling, since nothing refers to them. Once you
> have them listed in your tag database (ie you've created files that
> mention them in .git/refs/tags or something), you can tell fsck about
> them, and fsck won't complain.
>
> Something like
>
> fsck-cache --unreachable $(cat .git/refs/*/*)
>
> would do it (and depending on exactly how cogito ends up recording them).
great.
Dave
next prev parent reply other threads:[~2005-04-28 23:39 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
2005-04-28 22:06 ` Dave Jones
2005-04-28 22:22 ` Linus Torvalds
2005-04-28 23:44 ` Dave Jones [this message]
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=20050428234451.GB1730@redhat.com \
--to=davej@redhat.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.