Kendall Bennett wrote:
> 3. If it is the date and time when you check it out (I hope!) then
> how does it track this information? I need to be able to reset this
> when I check the files into Perforce so that CVS knows the files have
> not been changed even though the date and time may have changed.
It uses the date stamps as a hinting mechanism only, the decision as to whether a file
has changed or not is made with a diff. I believe (someone correct me if I'm wrong)
that it elides this check if the date stamp indicates that the file hasn't changed
since the last checkout. This is generally the Right Thing in most circumstances;
just make sure your clocks are set right. :)
> 4. Will a 'cvs update .' correctly update files whose date and time
> has been changed, but whose contents has not?
Yes. Again, the only way to get in trouble here is to fake the date stamps to
indicate that the file was last changed _before_ the last checkout. You will notice
performance issues, though, if it needs to diff (actually, I think the "has-changed"
test is done with a checksum) over the network for every file.
> 5. How are branches handled in CVS. Is there an easy easy way to
> automatically merge sources in one branch to another branch, for
> propagating bug fixes and updates from the development tree to the
> release tree and vice versa?
Automatically, no. There are bunches of tools available to do interactive merging,
however. I've never used them. :)
> 6. How does checkin's of multiple files at a time in CVS get
> handled? Does it properly track the list of files in that checkin as
> an entity, so that that change can easily be merged as a single
> entity from the development branch to the release branch or vice
> versa (for bug fixes etc)?
No. Each file checkin will have the same log entry, but there's not way to ask "give
me all the other files that changed in the same checkin". Even worse: modifications
to the repository are atomic with respect to FILES only. It's entirely possible for a
checkin to bail half way through, or for two simultaneous checkins to kill each other
on files that can't be merged. This is a legitimate wart, IMHO.
> 7. How can I check out just a 'portion' of a particular CVS branch
> onto my hard drive. I would like to be able to only check out the
> Mesa/src, Mesa/include and Mesa/src-glu directories
It works exactly like you'd hope:
cvs checkout The/SubDir/You/Would/Like
Doing cvs update, by default, doesn't recurse through directories that you haven't
checked out (specify the -d option to get that behavior).
Andy
--
Andrew J. Ross NextBus Information Systems
Software Engineer Emeryville, CA
[EMAIL PROTECTED] http://www.nextbus.com
(510)652-1303x19 Why Wait?
_______________________________________________
Mesa-dev maillist - [EMAIL PROTECTED]
http://lists.mesa3d.org/mailman/listinfo/mesa-dev
