git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git fsck, badDate: invalid author/committer line - bad date

From
Jeff King <peff@peff.net>
Date
Oct 31, 2019, 19:30 UTC
Message-ID
<20191031193018.GB12834@sigill.intra.peff.net>
In-Reply-To
<20191031101539.GY4348@szeder.dev>
On Thu, Oct 31, 2019 at 11:15:39AM +0100, SZEDER Gábor wrote:
> However, I don't know how to tell about the skiplist file to GitHub,
> or any other Git hosting service for that matter.
You can contact GitHub support. The usual procedure is:
  1. Find out if rewriting is an option (i.e., if the history isn't
     already widely published), and walk the user through cleaning up
     the history if that's an option.
  2. For established history, we'll sometimes relax the fsck checks
     temporarily to allow it to be pushed (it depends on the exact
     failing check, but this one is mostly cosmetic and would be OK).
-Peff
Previous: Eric Sunshine
Message 6 of 6 in “git fsck, badDate: invalid author/committer line - bad date”
  1. Olaf HeringOct 31, 2019
  2. SZEDER GáborOct 31, 2019
  3. Olaf HeringOct 31, 2019
  4. SZEDER GáborOct 31, 2019
  5. Eric SunshineOct 31, 2019
  6. Jeff KingOct 31, 2019

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.