> On Nov 27, 2016, at 3:43 PM, Anton Lundin <gla...@acc.umu.se> wrote: > > On 27 November, 2016 - Robert C. Helling wrote: > >> Hi >> >>> Am 27.11.2016 um 22:34 schrieb Rick Walsh <rickmwa...@gmail.com>: >>> >>> http://git.subsurface-divelog.org/index.cgi?p=subsurface.git;a=summary >>> shows that the latest commit in Master is >>> 4d0d37b6903a65ade442fece35238d1670522df2 Show effective gradient factors >>> for VPMB-plans, but when I run git pull on my machine, the latest commit is >>> four earlier: 2aeb2b8d8b045b317efa595aabb356680dbf4978 Small fix for Ubuntu >>> builds >> >> Same here. >> > > git ls-remote git://subsurface-divelog.org/subsurface HEAD > 2aeb2b8d8b045b317efa595aabb356680dbf4978 HEAD > git ls-remote https://github.com/dirkhh/subsurface.git HEAD > 4d0d37b6903a65ade442fece35238d1670522df2 HEAD > > 2aeb2b8 Small fix for Ubuntu builds > ... > 4d0d37b Show effective gradient factors for VPMB-plans > > > So, something in your push-magic is br0ken.
Actually, that wasn't it at all. The redirection of ports was off. I push via ssh but you checked via the git and http protocols. http and ssh were pointing to the new server, but git was still pointing to the old server. Oops. Thanks for catching this. /D _______________________________________________ subsurface mailing list subsurface@subsurface-divelog.org http://lists.subsurface-divelog.org/cgi-bin/mailman/listinfo/subsurface
