"cvs checkout" means you want to check out the files that you need from the CVS repository into your workspace, or sandbox. These files are essentially your working copies of the files in the repository. Any changes you make to these files from now on will only exist on YOUR sandbox, NOT the repository. You commit your changes to the repository by doing a "cvs commit."
Ok so far? Now say one of the files you checked out (I assume you know what this means now :) is file.cpp. But later on someone else checked this out, made some changes, and committed the changes in the repository. Now YOUR copy of file.cpp does NOT the other person's changes correct? Now to update your copy with the other person's changes, you do a "cvs update." So now when you do a "cvs commit", you include BOTH the other person's changes AND your changes. If you do a "cvs commit" without doing a "cvs update," you will have eclipsed the other person's changes. Make sense? -chris -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Irving Kimura Sent: Wednesday, May 26, 2004 1:31 PM To: [EMAIL PROTECTED] Subject: Newbie: update vs. checkout I'm sorry for this very stupid question, but after spending a lot of time reading the CVS documentation, I still don't understand what *exactly* is the difference between update and checkout. Could someone explain it to me? Thanks! Irv _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs _______________________________________________ Info-cvs mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/info-cvs
