In todays 2.6 git repo, I see the following:
$ fsck-cache expect dangling commits - potential heads - due to lack of head information dangling commit 897f5ab2cd733a77a2279268262919caa8154b9d dangling tree c39ae07f393806ccf406ef966e9a15afc43cc36a
The dangling commit is the current head - that's fine. However, what's this dangling tree?
It appears to have come in from Linus' tree on kernel.org this morning.
(above from cogito 0.8)
-- Russell King
Re: dangling trees
On Thu, May 05, 2005 at 02:12:25PM +0100, Russell King wrote:
> In todays 2.6 git repo, I see the following: > > $ fsck-cache > expect dangling commits - potential heads - due to lack of head information > dangling commit 897f5ab2cd733a77a2279268262919caa8154b9d > dangling tree c39ae07f393806ccf406ef966e9a15afc43cc36a > > The dangling commit is the current head - that's fine. However, > what's this dangling tree? > > It appears to have come in from Linus' tree on kernel.org this morning. > > (above from cogito 0.8)
As an additional note, the ID does not correspond with any tags or heads:
.git/refs/heads/master:897f5ab2cd733a77a2279268262919caa8154b9d .git/refs/heads/origin:897f5ab2cd733a77a2279268262919caa8154b9d .git/refs/tags/v2.6.11:5dc01c595e6c6ec9ccda4f6f69c131c0dd945f8c .git/refs/tags/v2.6.11-tree:5dc01c595e6c6ec9ccda4f6f69c131c0dd945f8c .git/refs/tags/v2.6.12-rc2:9e734775f7c22d2f89943ad6c745571f1930105f .git/refs/tags/v2.6.12-rc3:0397236d43e48e821cce5bbe6a80a1a56bb7cc3a
-- Russell King
Re: dangling trees
On Thu, May 05, 2005 at 02:17:10PM +0100, Russell King wrote:
> > dangling tree c39ae07f393806ccf406ef966e9a15afc43cc36a > > > > The dangling commit is the current head - that's fine. However, > > what's this dangling tree? > > > > It appears to have come in from Linus' tree on kernel.org this morning. > > > > (above from cogito 0.8) > > As an additional note, the ID does not correspond with any tags or > heads: > > .git/refs/heads/master:897f5ab2cd733a77a2279268262919caa8154b9d > .git/refs/heads/origin:897f5ab2cd733a77a2279268262919caa8154b9d > .git/refs/tags/v2.6.11:5dc01c595e6c6ec9ccda4f6f69c131c0dd945f8c
Those are tag objects.
$ git-cat-file tag 5dc01c595e6c6ec9ccda4f6f69c131c0dd945f8c | head -3 object c39ae07f393806ccf406ef966e9a15afc43cc36a type tree tag v2.6.11-tree
--L
Re: dangling trees
On Thu, May 05, 2005 at 02:12:25PM +0100, Russell King wrote:
> $ fsck-cache > expect dangling commits - potential heads - due to lack of head information
See the message on 'nightly kernel builds' - you are seeing 2.6.11 probably.
-- http://www.PowerDNS.com Open source, database driven DNS Software http://netherlabs.nl Open and Closed source services
Linus TorvaldsRe: dangling trees
On Thu, 5 May 2005, Russell King wrote:
> > In todays 2.6 git repo, I see the following: > > $ fsck-cache > expect dangling commits - potential heads - due to lack of head information > dangling commit 897f5ab2cd733a77a2279268262919caa8154b9d > dangling tree c39ae07f393806ccf406ef966e9a15afc43cc36a > > The dangling commit is the current head - that's fine. However, > what's this dangling tree?
That's the 2.6.11 tree, which I added to have a previous real release to diff against.
> It appears to have come in from Linus' tree on kernel.org this morning.
Yes. You can make (my) fsck shut up with something like
refs=.git/refs/*/* git-fsck-cache $refs
but that assumes that cogito has been updated to the newer fsck that understands to follow tags (not just parse them, but also add the "tag refers to object xxx" info to its internal tree of trust). I don't think that has happened yet.
In the meantime, just ignore it.
Linus