From 7037f0609e5350ac2c785fedd2c94c29a6b73bfd Mon Sep 17 00:00:00 2001 From: Eric Andersen Date: Thu, 11 Dec 2003 07:16:11 +0000 Subject: Rework the website --- docs/uclibc.org/cvs_howto.html | 44 ++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 44 insertions(+) create mode 100644 docs/uclibc.org/cvs_howto.html (limited to 'docs/uclibc.org/cvs_howto.html') diff --git a/docs/uclibc.org/cvs_howto.html b/docs/uclibc.org/cvs_howto.html new file mode 100644 index 000000000..cff3a353c --- /dev/null +++ b/docs/uclibc.org/cvs_howto.html @@ -0,0 +1,44 @@ + + + +

How to use CVS

+ + +If you want to know all the gory details, you will want to visit +the CVS main web page.

+For the impatient, the following is probably about all you need to know: +

+ +

+ 
cvs checkout -c
+
Will list the modules available for checkout + 
cvs checkout < module name >
+
Will checkout the named module + 
cvs co < module name >
+
Same thing + 
cvs update
+ +
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. + 
cvs up
+
Same thing + 
cvs update < file name >
+
Same thing but for just the named file(s)/directory(s). + 
cvs commit
+
Will check in all your work. + 
cvs add < file name >
+ +
Adds the named file/directory into CVS + 
cvs remove < file name >
+
Removes the named file/directory from the upstream repository. + 
cvs rm < file name >
+
Same thing + 
cvs log < file name >
+
+ + + + -- cgit v1.2.3