uClibc CVS Read/Write Instructions

From 4ddd797e60f6222cd5b61aacb503ca755c8ea203 Mon Sep 17 00:00:00 2001 From: Eric Andersen Date: Mon, 11 Mar 2002 07:49:07 +0000 Subject: Fix broken links --- docs/uclibc.org/cvs_write.html | 116 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 116 insertions(+) create mode 100644 docs/uclibc.org/cvs_write.html (limited to 'docs/uclibc.org/cvs_write.html') diff --git a/docs/uclibc.org/cvs_write.html b/docs/uclibc.org/cvs_write.html new file mode 100644 index 000000000..b0d7ff01c --- /dev/null +++ b/docs/uclibc.org/cvs_write.html @@ -0,0 +1,116 @@ + + + + +uClibc CVS Read/Write Instructions + + + + + + + +

Accessing the uClibc CVS Repository

+ + + + + + +

+ + B u s y B o x + +

+ + + + + + + +

+ + CVS Read/Write Access + +

+ + +If you want to be able to commit things to CVS, first contribute some +stuff to show you are serious. Then, very nicely ask +Erik Andersen if he will set you up with +an account. To access CVS, you will want to add the following to set up your environment: +

+$ export CVS_RSH=/usr/bin/ssh
+$ export CVSROOT='username@cvs.uclibc.org:/var/cvs'

+
+It goes without saying you must change username to your own +username... +

+ +To obtain commit access, you will need to demonstrate you are +serious by submitting a few good patches first. Then, you will need to +select a user-name to use when committing stuff, and finally, you will +need to send me the username you have selected, an ssh key, and the email +address where you prefer email to be sent (I will forward any email sent +to you, but not store it). + +

+Note that if you would prefer to keep your communications with me +private, you can encrypt your email using my +public key. + + + + +

+ + + + +

+ + + + + + + + + + + + + + + +

+ + Mail all comments, insults, suggestions and bribes to + Erik Andersen
+ The Busybox logo is copyright 1999-2002, Erik Andersen. + +

+ + + + + + + -- cgit v1.2.3