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
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
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