1. Commit The Changes
By:
Swetha Kendyala

2. Introduction
Committing files is the main part of CVS. New revisions span from committing newer versions of code or documents.

3. When to commit?
Once we’re happy with our changes, we need to commit them to the repository.
We can commit all our changes, or changes to an individual file (often dangerous).
Commit to mark a working state that you might want to return to later.
Commit to backup your sources.

4. Commit
When the local copy changes, “commit” the changes to the repository

5. Checking In Example % cvs commit cvs commit: Examining .
Checking in Makefile;
…/Makefile,v <-- Makefile
new revision 1.2; previous revision 1.1
RCS file: …/README,v
done
Checking in README:
…/README,v <-- README
initial revision 1.1
Checking in hello.C
…/hello.C,v <-- hello.C

6. Angela commits changes
What can go wrong?
Angela commits changes
Angela commits her changes to the master repository

7. Hassan tries to commit changes
Hassan has made changes to a different part of the repository, and tries to commit: he isn’t allowed to because the repo files are newer.

8. Conclusion: partners commit broken code don’t let them
Some Suggestions:
partners commit broken code don’t let them
back out changes
Whenever you commit a file, you must specify a log message with the commit. If you do not have the –m “message” part, a text editor will appear and ask you to submit a log message. To set this editor, use the environmental variable:
>export EDITOR=vim

9. Questions???