login
Header Space

 
 

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

Score:
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Johannes Schindelin <Johannes.Schindelin@...>
Cc: <git@...>
Date: Sunday, July 22, 2007 - 5:42 pm

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


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'


-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[PATCH] fsck --lost-found: write blob's contents, not their ..., Johannes Schindelin, (Sun Jul 22, 4:20 pm)
Re: [PATCH] fsck --lost-found: write blob's contents, not th..., Junio C Hamano, (Sun Jul 22, 5:42 pm)
Re: [PATCH] fsck --lost-found: write blob's contents, not th..., Johannes Schindelin, (Sun Jul 22, 5:52 pm)
speck-geostationary