Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search archives
  Advanced Search

Re: Stuck cvs lock on anoncvs repository

  • From: Dave Page <dpage(at)pgadmin(dot)org>
  • To: Magnus Hagander <magnus(at)hagander(dot)net>
  • Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, "Marc G. 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
  • Subject: Re: Stuck cvs lock on anoncvs repository
  • Date: Sun, 28 Jun 2009 09:28:09 +0100
  • Message-id: <937d27e10906280128q275be5e6mc2271dfe8062ad8e@mail.gmail.com> <text/plain>
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.

-- 
Dave Page
EnterpriseDB UK:   http://www.enterprisedb.com
Home | Main Index | Thread Index

Privacy Policy | About PostgreSQL
Copyright © 1996 – 2012 PostgreSQL Global Development Group