Re: [PATCH] fsck --lost-found: write blob's contents, not their SHA-1

From: Junio C Hamano <gitster@pobox.com>
Date: Jul 22, 2007, 21:42 UTC
Message-ID: <7vodi4qfnx.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <Pine.LNX.4.64.0707222120100.14781@racer.site>

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

> When looking for a lost blob, it is much nicer to be able to grep
> through .git/lost-found/other/* than to write an inefficient loop
> over the file names.  So write the contents of the dangling blobs,
> not their object names.

I think this is an idea to solve a good problem, but if we go this route, the need for us to worry about expiring lost-found entries would become more urgent, I suspect.

And when you think about expiring lost-found entries, another possible solution emerges. If we teach git-prune to remove the corresponding entry from lost-found/other when it removes a loose blob from the object store, then we can easily and safely do this instead:

	$ cat .git/lost-found/other/* |
	  xargs -r git grep 'the word to look for'