[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: cvs commit behavior

From: Mark D. Baushke
Subject: Re: cvs commit behavior
Date: Fri, 07 Mar 2003 08:21:17 -0800

Andy Harrison <address@hidden> writes:

> Sorry, I'm new to cvs.  I just want to verify this is correct behavior.
> I got a cvs pserver working and all that. I added something to the
> tree to try it out. I check it out, add a line, commit. When I
> manually look in the CVSROOT, it only shows the ,v file updated. Back
> in my home dir, I rm -rf the dir I had checked out from cvs. check out
> the module again, and the line I added and committed is indeed there.
> I just want to make sure this is normal that cvs commits only update
> the ,v file.

If you checkout a module onto your local machine, then locally modify
that file and commit it, the ,v file is the only one that will normally
be updated on the server. Your local copy will remain modified or be
additionally modified if you have an rcs keyword-id in it. Anyone who
does an update of the module will get the updated version of the file.

There are some 'database' files that will be rebuild on the server if
the module is the CVSROOT and the file is one of the special
administrative files, then a copy of the HEAD revision of that file will
be checked out into the repository CVSROOT directory.

See appendex C in the reference manual for the list of administrative

You may add a file in CVSROOT to the list of administrative files that
gets checked out into the CVSROOT on a commit by adding the filename to
the checkoutlist file.

        Good luck,
        -- Mark

reply via email to

[Prev in Thread] Current Thread [Next in Thread]