Re: Stuck cvs lock on anoncvs repository

From: "Marc G(dot) Fournier" <scrappy(at)hub(dot)org>
To: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
Cc: 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>, 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 00:09:19
Message-ID: 20090627210835.S56412@hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

On Sat, 27 Jun 2009, Alvaro Herrera wrote:

> Stefan Kaltenbrunner escribió:
>> Greg Stark wrote:
>>> do we not have --delete on the rsync command? why doesn't the problem
>>> go away on the next sync if we do?
>>
>> we do use --delete - but nobody commited after we tagged and before the
>> problem got reported so the regular on-commit code didn't kick in and
>> forced syncs only happen once a day.
>
> Are we worried about bandwidth wastage that we don't run it more often?

More often then when ppl commit? What would be the point to that?

AT least, the way I understood it setup, when someone does a commit, it
initiates a push to the anoncvs repository ...

----
Marc G. Fournier Hub.Org Networking Services (http://www.hub.org)
Email . scrappy(at)hub(dot)org MSN . scrappy(at)hub(dot)org
Yahoo . yscrappy Skype: hub.org ICQ . 7615664

In response to

Responses

Browse pgsql-www by date

  From Date Subject
Next Message Robert Haas 2009-06-28 01:49:51 Re: [HACKERS] pull raw text of a message by message-id
Previous Message Alvaro Herrera 2009-06-27 22:23:23 Re: Stuck cvs lock on anoncvs repository