Re: cannot update to the latest CVS sources - Mailing list pgsql-hackers

From Dave Page
Subject Re: cannot update to the latest CVS sources
Date
Msg-id 937d27e10906120715q63cead9bx15c2962cf452e5d8@mail.gmail.com
Whole thread Raw
In response to cannot update to the latest CVS sources  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: cannot update to the latest CVS sources  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
List pgsql-hackers
On Fri, Jun 12, 2009 at 9:45 AM, Fujii Masao<masao.fujii@gmail.com> wrote:
> Hi,
>
> $ cvs update
> ....
> cvs update: Updating src/backend/commands
> cvs update: [08:32:37] waiting for anoncvs's lock in
> /projects/cvsroot/pgsql/src/backend/commands
> cvs update: [08:33:07] waiting for anoncvs's lock in
> /projects/cvsroot/pgsql/src/backend/commands
> cvs update: [08:33:37] waiting for anoncvs's lock in
> /projects/cvsroot/pgsql/src/backend/commands
> cvs update: [08:34:07] waiting for anoncvs's lock in
> /projects/cvsroot/pgsql/src/backend/commands
> cvs update: [08:34:37] waiting for anoncvs's lock in
> /projects/cvsroot/pgsql/src/backend/commands
> cvs update: [08:35:07] waiting for anoncvs's lock in
> /projects/cvsroot/pgsql/src/backend/commands
>
> The cvs's lock remains held? Why?

Please try now.

-- 
Dave Page
EnterpriseDB UK:   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: cannot update to the latest CVS sources
Next
From: "Kevin Grittner"
Date:
Subject: Re: cannot update to the latest CVS sources