From: Junio C Hamano Date: Thu, 15 Sep 2005 19:31:24 GMT Subject: Re: [PATCH 0/4] Recovery after interrupted HTTP(s) fetch Message-ID: <7vu0gmyvoz.fsf@assigned-by-dhcp.cox.net> In-Reply-To: Matthias Urlichs writes: > Personally I'd rather combine the two. The point being, broken > repositories do happen -- for instance, when the file system is > inconsistent after a crash, or when the referent of an info/alternates > directory vanishes. :-/ > > I'd rather have a simple repair flag than do a "download everything again > and then throw most of it away" job when something like that happens. If you are talking about disaster recovery, wouldn't you rather clone the remote into a clean repository, and fetch what are salvageable from the potentially corrupt old repository into this clean repository you know is OK? I think that would suggest that you do not need another "download everything again" added to git-http-fetch. You can already run git-clone from the remote to "download everything again", and then git-fetch from the repository being salvaged.