| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, "Marc G(dot) Fournier" <scrappy(at)hub(dot)org>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, Greg Stark <gsstark(at)mit(dot)edu>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Dave Page <dpage(at)pgadmin(dot)org>, pgsql-www(at)postgresql(dot)org |
| Subject: | Re: Stuck cvs lock on anoncvs repository |
| Date: | 2009-06-28 14:17:50 |
| Message-ID: | 7040.1246198670@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> writes:
> Tom Lane wrote:
>> One thing I'm wondering is why cvs is taking out locks at all, since
>> it's certainly not committing to the repository. I guess even a "cvs
>> update" locks things momentarily, but can we prevent that?
> the problem is that we transferred the locks from cvs.postgresql.org to
> anoncvs.postgresql.org which confused cvs running on anoncvs.
Ah, now I understand. Yes, sounds like a simple --exclude will fix it.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | webmaster | 2009-06-29 14:00:00 | PostgreSQL moderation report: 2009-6-29 |
| Previous Message | Robert Haas | 2009-06-28 12:06:02 | Re: Stuck cvs lock on anoncvs repository |