|
Home
About
Discussion
Recent Discussion
Create New Topic
Membership
Join Now
Login
|
Re: Setting up CVS to update FrontierKernel source
Just a couple of notes:
- When you first mentioned backups, I thought "you don't need that
with version control", but then later you indicated that you only had
read-only access. So this note is only for those with commit
access: generally you don't need backup because one should "commit
early, commit often" (working, tested units of work, of course ;-)
- Yes, CVS will replace missing files when you "update" your
working copy. It won't "revert" changes made to files, though it
may try to merge new changes from the repository. Naturally
enough, the easy way to revert a file in CVS is to remove it and then
run update.
- No, you will generally not need branches. You can run
"diff" to see differences between your working copy and the
repository. The GUI may have a "create patch" option, which is
equivalent to "cvs diff >mychanges.patch" at the command line for
creating patches that can be sent to the maintainers. (There's
some good conventions for creating patches or using multiple working
copies for different ongoing changes, ping me by email if/when you're
interested.)
- Another CVS GUI I've heard good things about is TortoiseCVS, it
integrates with Windows Explorer. Fwiw, I use the command line
only, there's only a handful of commands used on a regular basis.
|
