corrupt repos does not return error with `git fsck`

Wed, 20 May 2015 09:24:13 -0700 


Hi,

Clone the repos https://github.com/fmitha/SICL.

Then

    git show 280c12ab49223c64c6f914944287a7d049cf4dd0

gives

    fatal: bad object 280c12ab49223c64c6f914944287a7d049cf4dd0

But

    git fsck

gives

    Checking object directories: 100% (256/256), done.
    Checking objects: 100% (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 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

Reply via email to