corrupt repos does not return error with `git fsck`

% (49356/49356), done. So `git fsck` does not return an error, though the repos is corrupt. This may be of interest to the developers. Please CC me on any reply, I'm not subscribed to the list. Thanks. Regards, Faheem Mitha -- To unsubscribe from

Re: [PUB]corrupt repos does not return error with `git fsck`

On Wed, 20 May 2015, Stefan Beller wrote: On Wed, May 20, 2015 at 11:24 AM, Faheem Mitha fah...@faheem.info wrote: So, is the repos corrupt or not? Also, I don't understand why you say There is no file 28/0c... however. Why would you expect there to be? I don't see it mentioned

Re: [PUB]corrupt repos does not return error with `git fsck`

On Wed, 20 May 2015, Matthieu Moy wrote: Faheem Mitha fah...@faheem.info writes: Hi, Clone the repos https://github.com/fmitha/SICL. Then git show 280c12ab49223c64c6f914944287a7d049cf4dd0 gives fatal: bad object 280c12ab49223c64c6f914944287a7d049cf4dd0 It seems

Re: [PUB]corrupt repos does not return error with `git fsck`

. Regards, Faheem Mitha -- To unsubscribe from this list: send the line unsubscribe git in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html