Comment 11 for bug 1337735

It's actually not okay, it looks like newer Git versions just quietly make educated guesses when they run into this issue... I can reproduce it remotely with clone --mirror and fsck:

    fungi@dhole:~$ git clone --mirror git://git.openstack.org/openstack/neutron-specs.git
    Cloning into bare repository 'neutron-specs.git'...
    remote: Counting objects: 4632, done.
    remote: Compressing objects: 100% (1563/1563), done.
    remote: Total 4632 (delta 3105), reused 4540 (delta 3044)
    Receiving objects: 100% (4632/4632), 970.26 KiB | 816.00 KiB/s, done.
    Resolving deltas: 100% (3105/3105), done.
    Checking connectivity... done.
    fungi@dhole:~$ cd neutron-specs.git/
    fungi@dhole:~/neutron-specs.git$ git fsck
    Checking object directories: 100% (256/256), done.
    error in commit 5909192d566e994b2c2d29a54e5f283d8c2a51b5: invalid author/committer line - bad date
    Checking objects: 100% (4632/4632), done.