Brendan J Simon writes:
Why does cvs need to create an EmptyDir when I want to checkout files
from the repository to a fresh sandbox on my local machine
When you checkout a directory tree, every directory in the tree must map
to some directory in the repository. When there's no
On Mon, Mar 26, 2001 at 11:17:29AM -0500, Larry Jones wrote:
Once [CVSROOT/Emptydir] has been created
(by whatever means), there's no longer any need to have CVSROOT be
writable for the sake of Emptydir.
Is it also the case that Emptydir itself doesn't need to be
writable?
--
| | /\
|-_|/
Eric Siegerman writes:
Is it also the case that Emptydir itself doesn't need to be
writable?
If you're not using LockDir in CVSROOT/config, Emptydir needs to be
writable so that users can create lock files in it; if you are using
LockDir to put the lock files elsewhere, then it does not need
I have been using a cvs server on a Win2000 machine and now shifting the
repository to a Debian Linux PowerPC machine. I did this some time ago
as a test and it worked fine. When trying the same thing recently I
found that I had permission problems trying to checkout a test module.
I