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

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

From
Stefan Beller <sbeller@google.com>
Date
Jun 20, 2016, 18:46 UTC
Message-ID
<CAGZ79kZL-ZY_0hZx9uA-ObPvMiD+EWvJYQa+OfCeQe2RLOPECA@mail.gmail.com>
In-Reply-To
<CAM+g_NswH8fd8aFPEHfSLYnZWptNU2GX=xTWpehzjTJfJM_GfQ@mail.gmail.com>
On Mon, Jun 20, 2016 at 11:41 AM, Norbert Kiesel <nkiesel@gmail.com> wrote:
Show 9 quoted lines
> 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.
git-pull doesn't care about the commit/author date/time at all.

All it takes into consideration is the graph structure of the commits on the local and the remote branch, i.e. Are there any commits on the remote branch that are not part of the local branch history?

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

You need to see if that commit is part of the history of the remote branch you pulled.

Show 7 quoted lines
>
> For the record: the faulty commit is
> https://github.com/seandepagnier/weather_routing_pi/commit/23c07cc5d2be7ce68349f4b3719b6fa6fe90e0bf
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous: Norbert KieselNext: Norbert Kiesel
Message 2 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.