Hmm. On closer inspection that commit 23c07cc that github shows with date 2152-06-19 is already in my local branch. I got confused because locally it is shown with a different date: `git log -1 --format='%ci' 23c07cc` shows "2106-02-07 06:28:56 -40643156" which is invalid. My system is running Debian unstable 64bit. Is git using the time rendering methods from the C library (glibc 2.22-12)? On Mon, Jun 20, 2016 at 11:46 AM, Stefan Beller <sbeller@xxxxxxxxxx> wrote: > On Mon, Jun 20, 2016 at 11:41 AM, Norbert Kiesel <nkiesel@xxxxxxxxx> wrote: >> 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. > >> >> 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@xxxxxxxxxxxxxxx >> More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html