forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Crossley <cross...@apache.org>
Subject Re: forrest cvs->svn
Date Wed, 10 Mar 2004 01:48:37 GMT
Brian W. Fitzpatrick wrote:
> David Crossley wrote:
> > Brian W. Fitzpatrick wrote:
> > <snip/>
> > > 
> > > FYI, I've had Noel change the xml-forrest CVS repository to read-only.
> > 
> > I am a Forrest committer and i tried to update my CVS working copy
> > today, as i have some uncommitted changes and i also wanted to
> > keep an up-to-date copy just prior to the SVN move.
> > 
> > I presumed that "read-only" meant that i could still do 'cvs update'
> > but it seems that i cannot. Is that the intended behaviour?
> > 
> > ------
> > cvs server: failed to create lock directory for `/home/cvs/xml-forrest'
> > ...
> 
> That was not the intent, but it is an unfortunate side-effect of the way
> CVS works (unless we're using LockDir, which we're not).
> 
> What would the Forrest committers like to do?  We could just flip it
> back to read-write if all the committers know that anything they commit
> to CVS is effectively going into the bitbucket.

Many thanks for your explanation and for your work on this.

Please leave it as "read-only" for the moment. We will talk
about it on forrest-dev@ and get back to infrastructure@ later
if we want anything different.

--David



Mime
View raw message