Filename Problems
CVS reserves some filenames for its own uses, and other filenames are included in the default ignore list.
If you have a file that CVS appears to be ignoring, check the
default
ignore list and any
cvsignore
files in your repository, home directory,
or sandbox. The default list is provided in Section 6.5.3.2 of Chapter 6. If the -I!
option to a
CVS command causes CVS to recognize the file, then you can be sure
the file is in a cvsignore
list. You can
temporarily force CVS to recognize an ignored file by stating it
explicitly as a command parameter.
CVS uses CVS
and Attic
directories in the repository. CVS prevents you from using the
filename CVS
but permits you to create files or
directories called Attic
. If you use an
Attic
directory and look in the repository, the
Attic
directory has files that
don’t exist on the trunk from the directory above
it, as well as those you are currently using in your sandbox version
of the Attic
. You should avoid using
Attic
as a file or directory name.
CVS may ignore a filename with a
#
or .#
prefix, as CVS reserves some files with
the prefix .#
for its own use. In the sandbox,
CVS uses the .#
prefix for copies of files it
has overwritten during a merge. In the repository, lock files start
with #
.
Another cause of filename problems is a conflict between the filesystem on a client computer and the filesystem on a repository. For example, filename case is significant in Linux and Unix filesystems, but not in Windows filesystems. If ...
Get Essential CVS now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.