On 24/10/10 Mike said:

> This weekend we're cutting over to use git for our source code control
> system.  I've imported about 20 years worth of previous history using
> "git cvsimport" (takes about four hours).  I then cloned the resulting
> repository onto five different machines (four Linux, one Solaris).
> I've set up a cron job to do a nightly "git fsck" on each of the five
> machines, and last night, two of the machines reported fsck errors on
> their initial run.  Here's a sample of the errors:

If you compare to a good copy, is Git correct? If it is, then the files were
corrupted somehow. 


Attachment: signature.asc
Description: Digital signature

Reply via email to