Re: Git lag

From: Dave Page <dpage(at)pgadmin(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Thom Brown <thom(at)linux(dot)com>, "w^3" <pgsql-www(at)postgresql(dot)org>
Subject: Re: Git lag
Date: 2013-03-10 18:54:30
Message-ID: CA+OCxoyw8MYjf4cyKM5kGpz--xQ44V_wvM-sUxmHDFCrj4tbHg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

On Sun, Mar 10, 2013 at 6:51 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Thom Brown <thom(at)linux(dot)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

In response to

Responses

Browse pgsql-www by date

  From Date Subject
Next Message Thom Brown 2013-03-10 18:54:46 Re: Git lag
Previous Message Tom Lane 2013-03-10 18:51:46 Re: Git lag