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

unable to pull from remote if commit date is in the future

From
NKNorbert Kiesel <nkiesel@gmail.com>
Date
Jun 20, 2016, 18:41 UTC
Message-ID
<CAM+g_NswH8fd8aFPEHfSLYnZWptNU2GX=xTWpehzjTJfJM_GfQ@mail.gmail.com>
Hi,

I'm following an upstream repo on github. Today morning I saw a new commit there, but a `git pull` in my clone did not fetch it and instead said "Already up-to-date.". On closer inspection, github reports commit time as 2152-06-19. The same project has some other commits with commit time in the future that were fetched. My guess is that happened when those commits got a child with commit date in the past.

Is there any way to force git pulling that request? (Perhaps I should try to tell git that it's really 2152?)

For the record: the faulty commit is https://github.com/seandepagnier/weather_routing_pi/commit/23c07cc5d2be7ce68349f4b3719b6fa6fe90e0bf

Next: Stefan Beller
Message 1 of 10 in “unable to pull from remote if commit date is in the future”
  1. Norbert KieselJun 20, 2016
  2. Stefan BellerJun 20, 2016
  3. Norbert KieselJun 20, 2016
  4. Jeff KingJun 20, 2016
  5. Norbert KieselJun 20, 2016
  6. Jeff KingJun 20, 2016
  7. Jeff KingJun 20, 2016
  8. Eric DeplagneJun 20, 2016
  9. Jeff KingJun 20, 2016
  10. Andreas SchwabJun 20, 2016

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.