-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The lines in the history file consist of fields separated by '|'
characters.
The first field: M3cd13118 indicates the type of operation ('M' is
commit from modified file) and the rest of this field is the
timestamp of the operation in hex. This
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
My understanding is that when you commit each folder is committed
individually. So when you commit something which covers
dirs, sub1 and
sub2, it actually gets run as 3 separate commits.
Yes, this is what I understood and what I
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Use the following CVS command:
cvs update -d -P
from the top directory of your sandbox.
The -d option tells CVS to create directories that have been added to
the repository that don't exist in your sandbox and the -P tells CVS
to delete directories
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If your cvs working directory is on an NT File System (NTFS)
partition, the problem may have been caused by the way windows stores
times for events in the system event log and files in the NTFS. For
details, see:
An easier way to look at the pserver client/server dialog is to define the
CVS_CLIENT_LOG environment variable with the base file name for the log on
the client. The client will create two files. Everything that the client
sends to the server is logged in filename.in and everything from the
The log_accum.pl script requires a companion script executed by the
commitinfo
trigger mechanism. The necessary script is commit_prep.pl (also included in
the contrib directory with log_accum.pl. If the commit_prep.pl script is
given the -r command line option, it will record the last directory
