diff options
| -rw-r--r-- | docs/uclibc.org/cvs_anon.html | 78 |
1 files changed, 78 insertions, 0 deletions
diff --git a/docs/uclibc.org/cvs_anon.html b/docs/uclibc.org/cvs_anon.html index ad9c8c87e..388626f39 100644 --- a/docs/uclibc.org/cvs_anon.html +++ b/docs/uclibc.org/cvs_anon.html @@ -79,6 +79,84 @@ able to commit any changes. Changes can be submitted for inclusion by posting them to the appropriate <a href="http://www.uclibc.org/mailman/listinfo/uclibc">mailing list</a>. +<!-- End of Table --> + +</TD></TR> +</TABLE> + + + +<TABLE WIDTH="95%" CELLSPACING=1 CELLPADDING=4 BORDER=1> +<TR><TD BGCOLOR="#ccccc0" ALIGN=center> + <A NAME="howto"> <BIG><B> + How to use CVS + </B></BIG></A> +</TD></TR> +<TR><TD BGCOLOR="#eeeee0"> + + +If you want to know all the gory details, you will want to visit +<a href="http://www.cvshome.org/">the CVS main web page</a>.<p> +For the impatient, the following is probably about all you need to know: +<p> + +<dl> + <dt><pre>cvs checkout -c</pre> + <dd>Will list the modules available for checkout + <dt><pre>cvs checkout < module name ></pre> + <dd>Will checkout the named module + <dt><pre>cvs co < module name ></pre> + <dd>Same thing + <dt><pre>cvs update</pre> + + <dd>Updates your local archive so it is in sync with the repository + -- your local updates are left intact. Tries to merge upstream updates + into your local updates. You will see the following tags when it is + updating your local repository: C means conflict, U means update, + P means patched, and M means modified. + <dt><pre>cvs up</pre> + <dd>Same thing + <dt><pre>cvs update < file name ></pre> + <dd>Same thing but for just the named file(s)/directory(s). + <dt><pre>cvs commit</pre> + <dd>Will check in all your work. + <dt><pre>cvs add < file name ></pre> + + <dd>Adds the named file/directory into CVS + <dt><pre>cvs remove < file name ></pre> + <dd>Removes the named file/directory from the upstream repository. + <dt><pre>cvs rm < file name ></pre> + <dd>Same thing + <dt><pre>cvs log < file name ></pre> + + <dd>Gives you the complete version history of what has happened to the named file(s). + Along with all tags, all commit messages, etc... + <dt><pre>cvs status < file name ></pre> + <dd>Gives you the current version number of the file(s) in question. + <dt><pre>cvs tag TAGNAME</pre> + <dd>Tags the versions of everything in the repository with the TAGNAME label. + <dt><pre>cvs tag TAGNAME < file name ></pre> + <dd>Tags the named file(s) in the repository with the TAGNAME label. + <dt><pre>cvs diff</pre> + + <dd>Gives you the difference between the local repository and the upstream repository. + <dt><pre>cvs diff < file name ></pre> + <dd>Same but for the named file(s). + <dt><pre>cvs diff -r 1.5 < file name ></pre> + <dd>Same but gives you the difference between the named file(s) and + version 1.5 of the named file(s). + <dt><pre>cvs diff -r TAGNAME < file name ></pre> + + <dd>Same but gives you the difference between the named file(s) and the + of the file tagged TAGNAME in the upstream repository. + <dt><pre>cvs rdiff -r TAGNAME module</pre> + <dd>Gives you a diff (that you can actually use with patch) between the current + version of module and the specified tagged version. + <dt><pre>cvs import < directory to import > < name for new module > start</pre> + <dd>Add a new module into the CVS archive. + <p> + +</dl> <!-- End of Table --> |