On Fri, Nov 21, 2014 at 03:03:08PM +0100, Jonas Gorski wrote: > >> I noticed that git over http(s) seems to get stale data (just done a > >> few minutes ago): > >> > >> ~$ git clone http://git.linux-mips.org/pub/scm/ralf/upstream-sfr.git > >> Cloning into 'upstream-sfr'... > >> ~$ cd upstream-sfr/ > >> ~/upstream-sfr$ git log -1 > >> commit 475d5928b79bb78326a645863d46ff95c5e25e5a > >> Merge: c6b7b9f 1062080 > >> Author: Ralf Baechle <ralf@xxxxxxxxxxxxxx> > >> Date: Sat Aug 2 00:07:03 2014 +0200 > >> > >> Merge branch '3.16-fixes' into mips-for-linux-next > > > > Odd - but I have an idea what might be wrong. > > > > Are you seeing this only with the upstream-sfr tree? > > Hadn't checked anything else, but looks like it also affects other trees: > > ~# git clone http://git.linux-mips.org/pub/scm/ralf/upstream-linus.git > Cloning into 'upstream-linus'... > ~$ cd upstream-linus/ > ~/upstream-linus$ git log -1 > commit 475d5928b79bb78326a645863d46ff95c5e25e5a > Merge: c6b7b9f 1062080 > Author: Ralf Baechle <ralf@xxxxxxxxxxxxxx> > Date: Sat Aug 2 00:07:03 2014 +0200 > > Merge branch '3.16-fixes' into mips-for-linux-next > > > (strangely the same commit) The issue is a stale info/refs on the server. This file normally gets updated when the hook hooks/post-update is ran which in turn calls git-update-server-info but that just didn't happen. Can you retry? Btw, why are you using http transport anyway? The git protocol should be more efficient. Ralf
