svn commit: branches/uClibc-nptl/docs/uclibc.org
sjhill at uclibc.org
sjhill at uclibc.org
Sat Sep 3 00:35:17 UTC 2005
Author: sjhill
Date: 2005-09-02 17:35:16 -0700 (Fri, 02 Sep 2005)
New Revision: 11319
Log:
Sync.
Modified:
branches/uClibc-nptl/docs/uclibc.org/developer.html
Changeset:
Modified: branches/uClibc-nptl/docs/uclibc.org/developer.html
===================================================================
--- branches/uClibc-nptl/docs/uclibc.org/developer.html 2005-09-02 23:06:30 UTC (rev 11318)
+++ branches/uClibc-nptl/docs/uclibc.org/developer.html 2005-09-03 00:35:16 UTC (rev 11319)
@@ -13,9 +13,15 @@
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 username
-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).
+to use when committing changes to SVN, you will need to send me the username
+you have selected, you must send me your preferred contact email address, and
+finally, you must send me an ssh version 2 DSA key with 1024 bits (the default)
+or more. If you do not currently have an ssh version 2 DSA key, you can
+generate a key using the command<pre>ssh-keygen -t dsa</pre> This will
+create the files <pre>/home/<USERNAME>/ssh/id_dsa
+/home/<USERNAME>/.ssh/id_dsa.pub</pre> You must then send the content
+of 'id_dsa.pub' to me so I can setup your account. The content of 'id_dsa'
+should of course be kept secret.
<p>
More information about the uClibc-cvs
mailing list