Hi Guys,
I am trying to figure out how to do some stuff with CVS, so would
like some advice. The things I am interested about as the following:
1. How does CVS manage files on your local disk? It appears to use
date and time stamps to determine whether a file has been modified.
If that is the case, does it simply use the date and time to
determine when a diff should be run to find out if the file has
actually been changed?
2. When CVS checks out files, do they get checked out with the date
and time of the files when they were checked into CVS, or the date
and time when the files were checked out by you?
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.
4. Will a 'cvs update .' correctly update files whose date and time
has been changed, but whose contents has not?
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?
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)?
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, since the
remainder of the repository is not used by us. This is one thing that
Perforce does really well, because I can change my client mapping to
only include the sources that I actually need to care about,
minimising the network traffic to the Perforce server.
Anyway. CVS seems to do a reasonable job, but it seems to me that it
falls short in a number of areas, especially when you start to have
multiple development branches going on at one time. As some of you
may know, Perforce makes free server licenses available for Open
Source development work, so Perforce could be used free of charge for
the Mesa software repository. I am curious how much resistance there
would be to getting the Mesa sources moved into Perforce (all the
change history can be kept, because Perforce uses the same RCS file
format internally and existing CVS and RCS archives can be easily
imported).
Regards,
+---------------------------------------------------------------+
| SciTech Software - Building Truly Plug'n'Play Software! |
+---------------------------------------------------------------+
| Kendall Bennett | Email: [EMAIL PROTECTED] |
| Director of Engineering | Phone: (530) 894 8400 |
| SciTech Software, Inc. | Fax : (530) 894 9069 |
| 505 Wall Street | ftp : ftp.scitechsoft.com |
| Chico, CA 95928, USA | www : http://www.scitechsoft.com |
+---------------------------------------------------------------+
_______________________________________________
Mesa-dev maillist - [EMAIL PROTECTED]
http://lists.mesa3d.org/mailman/listinfo/mesa-dev
