login
Header Space

 
 

Re: git-fsck/lost-found's speed vs git-prune's

Score:
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Mike Hommey <mh@...>
Cc: Junio C Hamano <gitster@...>, <git@...>
Date: Tuesday, September 18, 2007 - 7:13 am

Hi,

On Tue, 18 Sep 2007, Mike Hommey wrote:


That's why we should get rid of lost-found, and only keep the --lost-found 
option to git-fsck, to make it clear.

And I think that it is too rare that you lost objects and want to find 
them, to warrant a fast version of it.

Ciao,
Dscho

-
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:
git-fsck/lost-found's speed vs git-prune's, Mike Hommey, (Tue Sep 18, 5:09 am)
Re: git-fsck/lost-found's speed vs git-prune's, Junio C Hamano, (Tue Sep 18, 5:18 am)
Re: git-fsck/lost-found's speed vs git-prune's, Mike Hommey, (Tue Sep 18, 5:50 am)
Re: git-fsck/lost-found's speed vs git-prune's, Johannes Schindelin, (Tue Sep 18, 7:13 am)
Re: git-fsck/lost-found's speed vs git-prune's, Sam Vilain, (Tue Sep 18, 5:14 am)
speck-geostationary