OpenCores
URL https://opencores.org/ocsvn/or1k_old/or1k_old/trunk

Subversion Repositories or1k_old

[/] [or1k_old/] [trunk/] [linux/] [uClibc/] [docs/] [uclibc.org/] [cvs_anon.html] - Blame information for rev 1782

Details | Compare with Previous | View Log

Line No. Rev Author Line
1 1325 phoenix
<!--#include file="header.html" -->
2
 
3
 
4
<h3>Anonymous CVS</h3>
5
 
6
We allow anonymous (read-only) CVS access to everyone.  The first command you
7
need to run for anonymous CVS access is:
8
<pre>
9
cvs -d:pserver:anonymous@uclibc.org:/var/cvs login</pre>
10
<p>
11
CVS will prompt you for a password. Just press the Enter key (there is no
12
password for anonymous access).  This step only needs to be done once, the first
13
time you attempt to access CVS.
14
<p>
15
Once the login is complete, you can then check the list of available
16
CVS modules by running the following command (all on one line):
17
<pre>
18
cvs -z3 -d:pserver:anonymous@uclibc.org:/var/cvs co -c </pre>
19
 
20
<p>
21
If you wish, you can then check out a local copy of any of the
22
available modules.  The following is an example of how to grab
23
a copy of uClibc:
24
<pre>
25
    cvs -z3 -d:pserver:anonymous@uclibc.org:/var/cvs co -P uClibc</pre>
26
This will create a directory called <b>uClibc</b> in the current
27
directory.  This directory will contain the latest and greatest source
28
code for uClibc.
29
 
30
<p>
31
If you are not already familiar with using CVS, I recommend you visit
32
this quick <a href="/cvs_howto.html">Introduction to CVS</a>.
33
 
34
<p>
35
I usually create a ~/.cvsrc file with the following things in it, and I
36
recommend you should use the same:
37
<pre>
38
    -z3
39
    update -dP
40
    rdiff -u
41
    diff -ubBwpN
42
    checkout -P</pre>
43
 
44
<p>
45
Once you've checked out a copy of the source tree, you can update your
46
source tree at any time so it is in sync with the latest and greatest by
47
running the command:
48
<pre>
49
cvs update</pre>
50
 
51
Because you've only been granted anonymous access to the tree, you won't be
52
able to commit any changes. Changes can be submitted for inclusion by posting
53
them to the appropriate mailing list.  For those that are actively contributing
54
<a href="cvs_write.html">CVS write access</a> can be made available.
55
 
56
<!--#include file="footer.html" -->
57
 

powered by: WebSVN 2.1.0

© copyright 1999-2024 OpenCores.org, equivalent to Oliscience, all rights reserved. OpenCores®, registered trademark.