]> git.ipfire.org Git - thirdparty/git.git/commit - builtin-fsck.c
Git-prune-script loses blobs referenced from an uncommitted cache.
authorJunio C Hamano <junkio@cox.net>
Wed, 4 May 2005 08:33:33 +0000 (01:33 -0700)
committerJunio C Hamano <junkio@cox.net>
Wed, 4 May 2005 08:33:33 +0000 (01:33 -0700)
commitae7c0c92c0713307986bcd1fb54fa0694aae962a
tree74bcaa311990e35754b33479bf0bca7b5bfae16d
parentfd0ffd3ad12d6aa49b8ac2cce7728976d678cc63
Git-prune-script loses blobs referenced from an uncommitted cache.

(updated from the version posted to GIT mailing list).

When a new blob is registered with update-cache, and before the cache
is written as a tree and committed, git-fsck-cache will find the blob
unreachable.  This patch adds a new flag, "--cache" to git-fsck-cache,
with which it keeps such blobs from considered "unreachable".

The git-prune-script is updated to use this new flag.  At the same time
it adds .git/refs/*/* to the set of default locations to look for heads,
which should be consistent with expectations from Cogito users.

Without this fix, "diff-cache -p --cached" after git-prune-script has
pruned the blob object will fail mysteriously and git-write-tree would
also fail.

Signed-off-by: Junio C Hamano <junkio@cox.net>
fsck-cache.c
git-prune-script