public inbox for [email protected]
help / color / mirror / Atom feedFrom: Magnus Hagander <[email protected]>
To: Thom Brown <[email protected]>
Cc: Dave Page <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: w^3 <[email protected]>
Subject: Re: Git lag
Date: Sat, 13 Apr 2013 16:50:12 +0200
Message-ID: <CABUevExCmnohMdUwwmN24EdTbpyNFCaUymcYNcQbFnA=sBM9iw@mail.gmail.com> (raw)
In-Reply-To: <CABUevEwtGteDPeGbGi9=_KiRnYynY5k9i0RjF0F8teanNDQmQQ@mail.gmail.com>
References: <CAA-aLv5=zyB6S4Oa-xerqGPb3ek1qSOt7RLHBYTcuVX-pC-ACQ@mail.gmail.com>
<[email protected]>
<CA+OCxoyw8MYjf4cyKM5kGpz--xQ44V_wvM-sUxmHDFCrj4tbHg@mail.gmail.com>
<CAA-aLv6N81KcAL_8mb56EaVp3SdCoZsaLckyrPMYATKpRacJmA@mail.gmail.com>
<CABUevEwtGteDPeGbGi9=_KiRnYynY5k9i0RjF0F8teanNDQmQQ@mail.gmail.com>
List-Unsubscribe: <mailto:[email protected]?body=unsub%20pgsql-www>
On Tue, Mar 12, 2013 at 3:12 PM, Magnus Hagander <[email protected]> wrote:
> On Sun, Mar 10, 2013 at 7:56 PM, Thom Brown <[email protected]> wrote:
>> On 10 March 2013 18:54, Dave Page <[email protected]> wrote:
>>> On Sun, Mar 10, 2013 at 6:51 PM, Tom Lane <[email protected]> wrote:
>>>> Thom Brown <[email protected]> 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.
>>
>> Ah okay, yes, changed my .git/config to use git:// and all is well
>> again. Sorry for the noise.
>
> Not at all - Dave is actually at least partially wrong here, and I'm
> pretty sure I broke something. There were stil some issues before with
> http pulls, but they have unfortunately been made quite a lot worse :)
> I'll look at getting that sorted as soon a I can.
>
> Basically, there used to be an update issue. But now that we do full
> caching on the data, the fixes that are in there to work around the
> previous issue, don't necessarily work anymore...
With lots of delay, this should be fixed now. Sorry about that.
Other ways of pulling are still *faster* than http, but there should
be no extra delay in it.
--
Magnus Hagander
Me: http://www.hagander.net/
Work: http://www.redpill-linpro.com/
--
Sent via pgsql-www mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-www
view thread (7+ messages)
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: Git lag
In-Reply-To: <CABUevExCmnohMdUwwmN24EdTbpyNFCaUymcYNcQbFnA=sBM9iw@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox