From: Denis 'GNUtoo' Carikli <GNUtoo@cyberdimension.org>
To: Guenter Roeck <linux@roeck-us.net>,
"amy.shih" <amy.shih@advantech.com.tw>,
linux-hwmon@vger.kernel.org
Subject: git fsck broken due to "hwmon: (nct7904) Fix incorrect temperature limitation register setting of LTD."
Date: Thu, 31 Oct 2019 10:38:46 +0100 [thread overview]
Message-ID: <20191031103846.59a96454@primarylaptop.localdomain> (raw)
[-- Attachment #1: Type: text/plain, Size: 967 bytes --]
Hi,
When fetching linux[1] I have:
> $ git fetch origin
> remote: Enumerating objects: 119615, done.
> remote: Counting objects: 100% (119615/119615), done.
> remote: Compressing objects: 100% (22639/22639), done.
> error: object 4a2d78822fdf1556dfbbfaedd71182fe5b562194:
> badDateOverflow: invalid author/committer line - date causes integer
> overflow
> fatal: fsck error in packed object
> fatal: index-pack failed
According to gitweb[2], 4a2d78822fdf1556dfbbfaedd71182fe5b562194
corresponds to "hwmon: (nct7904) Fix incorrect temperature limitation
register setting of LTD.".
The issue seem to be that the "Author date" is "2085-06-18 15:57:19
+0000" which seems wrong.
Is there still time to fix this date?
References:
-----------
[1]git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
[2]https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4a2d78822fdf1556dfbbfaedd71182fe5b562194
Denis.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2019-10-31 9:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 9:38 Denis 'GNUtoo' Carikli [this message]
2019-10-31 13:16 ` git fsck broken due to "hwmon: (nct7904) Fix incorrect temperature limitation register setting of LTD." Guenter Roeck
2019-10-31 23:43 ` Denis 'GNUtoo' Carikli
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20191031103846.59a96454@primarylaptop.localdomain \
--to=gnutoo@cyberdimension.org \
--cc=amy.shih@advantech.com.tw \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux@roeck-us.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).