| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Dave Page <dpage(at)pgadmin(dot)org> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, "Marc G(dot) Fournier" <scrappy(at)hub(dot)org>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>, Greg Stark <gsstark(at)mit(dot)edu>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, "pgsql-www(at)postgresql(dot)org" <pgsql-www(at)postgresql(dot)org> |
| Subject: | Re: Stuck cvs lock on anoncvs repository |
| Date: | 2009-06-28 12:06:02 |
| Message-ID: | DB0570BD-F932-42A7-AD80-8CAA3597D9BF@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
On Jun 28, 2009, at 4:28 AM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
> On Sun, Jun 28, 2009 at 9:19 AM, Magnus
> Hagander<magnus(at)hagander(dot)net> wrote:
>
>> Remember that we can't push the timing too far on it, because the cvs
>> server will send out links to cvsweb right away, and those point to
>> the
>> anoncvs machine. 15 minutes *might* work, but not much more than
>> that.
>
> Yeuch. I often look at paches as soon as I see the email on
> -committers. Not having to wait for the changes to propagate was a
> definite improvement that I wouldn't want to see reverted.
>
> Besides, as far as I can see - Stefan's fix should resolve the issue
> entirely.
Triggered is definitely the way to go if it can be made robust, which
it sounds like it can. Otherwise, reducing the recovery time when
there *is* a problem is second-best.
...Robert
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-06-28 14:17:50 | Re: Stuck cvs lock on anoncvs repository |
| Previous Message | Dave Page | 2009-06-28 08:28:09 | Re: Stuck cvs lock on anoncvs repository |