[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091217183952.GC18217@ZenIV.linux.org.uk>
Date: Thu, 17 Dec 2009 18:39:52 +0000
From: Al Viro <viro@...IV.linux.org.uk>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: linux-kernel@...r.kernel.org
Subject: Re: [git pull] vfs pile 2
On Thu, Dec 17, 2009 at 10:16:08AM -0800, Linus Torvalds wrote:
> You can force git to get rid of those kinds of objects using
>
> git prune --expire=now
>
> or similar.
>
> [ Btw, things that _look_ unreachable may also be reachable through the
> reflog, which is not normally something you'd have in a bare repository
> anyway, but since you created the bare repo by copying/moving a non-bare
> one, you may well have reflog entries.
>
> Doing
>
> git reflog expire --all --expire=now
>
> should get rid of them, but you could also decide to just do it all the
> brute-force way with just "rm -rf logs" ]
reflog had been pruned already; still no effect. Moreover, after looking
through the loose objects, I've found several commits that are definitely
reachable from master and now from your tree as well. E.g.
objects/ea/ff8079d4f1016a12e34ab323737314f24127dd
is one of those - it's a commit and it's both in mainline *and* happens
to be tip of master. No questions about being unreachable and AFAICS
no reasons whatsoever to leave it as a loose object...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists