[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Renaming CVS/ directory (was: a few Q's)
From: |
Jim.Hyslop |
Subject: |
RE: Renaming CVS/ directory (was: a few Q's) |
Date: |
Fri, 24 Oct 2003 17:24:19 -0400 |
christos@zoulas.com [mailto:christos@zoulas.com] wrote:
> | > 6. add -D dirname flag, to specify an alternate
> directory name for
> | > cvs to store its administration files.
[...]
> Imagine you are working on a case insensive system and you
> have a directory
> called cvs. You can change -D to make the default directory
> .CVS for example
> to avoid the conflict.
Can I presume you have a really good reason why your source code directory
*must* be named "cvs"? I suppose importing a third-party source code would
be one reason, but that's the only one I can think of. Maybe I'm just not
imaginative enough.
In any case, I'd like to examine this feature a little before it gets
committed to the project, because I could foresee a host of problems,
depending on how it's implemented.
Can you explain how this feature works? For example, when do you specify it?
On checkout? What happens after that - do you have to use the same -D
command each time you issue any subsequent commands? Sounds a little
error-prone, if that's the case.
--
Jim
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- RE: Renaming CVS/ directory (was: a few Q's),
Jim.Hyslop <=