MIME-Version: 1.0
In-Reply-To: <8080.1362941506@sss.pgh.pa.us>
References: 
 <CAA-aLv5=zyB6S4Oa-xerqGPb3ek1qSOt7RLHBYTcuVX-pC-ACQ@mail.gmail.com>
	<8080.1362941506@sss.pgh.pa.us>
Date: Sun, 10 Mar 2013 18:54:30 +0000
Message-ID: 
 <CA+OCxoyw8MYjf4cyKM5kGpz--xQ44V_wvM-sUxmHDFCrj4tbHg@mail.gmail.com>
Subject: Re: Git lag
From: Dave Page <dpage@pgadmin.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Thom Brown <thom@linux.com>, "w^3" <pgsql-www@postgresql.org>
Content-Type: text/plain; charset=UTF-8
Precedence: bulk
Sender: pgsql-www-owner@postgresql.org

On Sun, Mar 10, 2013 at 6:51 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Thom Brown <thom@linux.com> writes:
>> There was a commit by Tom Lane approximately 30 mins ago, yet I'm
>> still unable to pull those changes into my local repo.  I'm told it's
>> up-to-date, but the latest commit was Magnus' pg_hba line number
>> logging change.
>
> That's really weird, because that commit did show up on
> http://git.postgresql.org/gitweb/?p=postgresql.git
> almost immediately.  I had the idea that gitweb was looking at the
> same anonymous-access git repo that non-committers should pull from.
> Maybe there's a third repo involved?

There's not, but there is some caching that can happen if you're
pulling the repo via http (I forget the exact details). Try using the
git:// URL instead Thom.

-- 
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


-- 
Sent via pgsql-www mailing list (pgsql-www@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-www