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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

On 2015-05-20 19:19, Matthieu Moy wrote:
> Faheem Mitha <faheem@xxxxxxxxxxx> writes:
> 
>> Clone the repos https://github.com/fmitha/SICL.
>>
>> Then
>>
>>     git show 280c12ab49223c64c6f914944287a7d049cf4dd0
>>
>> gives
>>
>>     fatal: bad object 280c12ab49223c64c6f914944287a7d049cf4dd0
> 
> It seems 280c12ab49223c64c6f914944287a7d049cf4dd0 is not an object in
> your repository. The good news it: I don't think you have a corrupt
> repository. What makes you think you have an object with identifier
> 280c12ab49223c64c6f914944287a7d049cf4dd0?

I had a similar problem some time ago and tracked it down to a graft that was active while pushing to the public repository. Maybe it's the same problem here?

Ciao,
Johannes
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]