From: Olaf Hering <olaf@aepfle.de>
To: "SZEDER Gábor" <szeder.dev@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git fsck, badDate: invalid author/committer line - bad date
Date: Thu, 31 Oct 2019 14:21:18 +0100 [thread overview]
Message-ID: <20191031142118.747693c1.olaf@aepfle.de> (raw)
In-Reply-To: <20191031101539.GY4348@szeder.dev>
[-- Attachment #1: Type: text/plain, Size: 471 bytes --]
Am Thu, 31 Oct 2019 11:15:39 +0100
schrieb SZEDER Gábor <szeder.dev@gmail.com>:
> However, I don't know how to tell about the skiplist file to GitHub,
> or any other Git hosting service for that matter.
Thanks for all the details.
Is there a way to "replay" a git repository, so that all the commit contents
and author/committer data are preserved? I think it is more important to have
a clean repository than to preserve irrelevant commit hashes.
Olaf
[-- Attachment #2: Digitale Signatur von OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-10-31 13:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-31 8:27 git fsck, badDate: invalid author/committer line - bad date Olaf Hering
2019-10-31 10:15 ` SZEDER Gábor
2019-10-31 13:21 ` Olaf Hering [this message]
2019-10-31 16:56 ` SZEDER Gábor
2019-10-31 17:12 ` Eric Sunshine
2019-10-31 19:30 ` Jeff King
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=20191031142118.747693c1.olaf@aepfle.de \
--to=olaf@aepfle.de \
--cc=git@vger.kernel.org \
--cc=szeder.dev@gmail.com \
/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).