zez.org: Version Control management with CVS - Part 2Nov 26, 2000, 12:00 (0 Talkback[s])
(Other stories by Jan Borsodi)
No-Size-Fits-All! An Application-Down Approach for Your Cloud Transformation REGISTER >
[ Thanks to Paul K Egell-Johnsen for this link. ]
"CVS is a Version Control System which helps multiple developers manage software projects. In this second part I'll show the basics of committing your changes to a project, adding new files, creating patches and explaining version numbers. For those of you who missed the first part you can read it here."
"Committing, the second of the two widely used CVS commands (the first is updating ), takes care of sending all your local changes to the CVS repository. To be able to commit your changes you need write access to the CVS repository, so any anonymous logins won't work.
"Before I start explaining the commit command I'll tell you a little secret that will make your committed work so much more appreciated."
0 Talkback[s] (click to add your comment)