Stephen Rothwell <[EMAIL PROTECTED]> writes:
>> Stephen Rothwell <[EMAIL PROTECTED]> writes:
>>
>> > The commit c594adad5653491813959277fb87a2fef54c4e05 is shown as
>> > "connected" (in Linus' tree, not one of my patches) by gitk, so I am happy
>> > that git prune did not get rid of it, but why d
On Wed, 31 Aug 2005 13:13:56 -0700 Junio C Hamano <[EMAIL PROTECTED]> wrote:
>
> Stephen Rothwell <[EMAIL PROTECTED]> writes:
>
> > The commit c594adad5653491813959277fb87a2fef54c4e05 is shown as
> > "connected" (in Linus' tree, not one of my patches) by gitk, so I am happy
> > that git prune did
Stephen Rothwell <[EMAIL PROTECTED]> writes:
> The commit c594adad5653491813959277fb87a2fef54c4e05 is shown as
> "connected" (in Linus' tree, not one of my patches) by gitk, so I am happy
> that git prune did not get rid of it, but why does fsck-cache report it as
> dangling?
Hmph. You ran fsck-
Hi all,
I have a tree that is a copy of Linus' git kernel tree in which I have
been doing development and pulling updates and rebasing my patches etc.
It now does this:
$ git fsck-cache
dangling tree 34d23b379f39922dff3cee671e28d41f3be56167
dangling blob 3eab2290b12a2cb683e4eadc20253bde37c84859
4 matches
Mail list logo