Re: /#cvs.lock): No such file or directoryctory for <somedirectory inrepository>

[Jim Page - emailsystems.com]

>    2. Re: /#cvs.lock): No such file or directoryctory for <some
>       directory inrepository> (Frederic Brehm)
>    4. Re: /#cvs.lock): No such file or directoryctory for <some
>       directory inrepository> (Geoff Beier)
>    6. Re: /#cvs.lock): No such file or directoryctory for
>       <somedirectory  inrepository> (Todd Denniston)

Fred, Geoff, Todd

You have obviously thought all this through, and I have quite a lot to think
about. It's clearly hopeless working with tools from multiple OSs on the
same sandbox, and I guess I have been lucky so far, that's all. I think my
preferred route will be to restrict tool usage to one or the other per
developer, as the alternatives - multiple sandboxes, branches seem to me to
add too much complexity and scope for error.

Thanks a lot for your input. The free software community validates itself
once again :)

Cheers
Jim


------------------------------------------------------------------------------------
Email the way you want it - scanned for viruses and unwanted content by 
emailsystems

Information regarding this service can be found at www.emailsystems.com