f46f1b4d8
Eric Andersen
2005-09-02
Subject
update the verbage describing what is needed for developer access
SOURCE BUG
This commit was genuinely broken at the time (not related to our build system): scripts/config/mkconfigs.c (2005-08-01 - 2006-10-05 arasi) uretilen bbconfigopts.h icine .config satirlarini kacissiz, ham newline'larla gömüyordu - gecerli C degildi, busybox'un kendi bb_mkdep araci bile parse edemiyordu (7d219aab7 ile duzeltildi, mkconfigs shell scripte cevrildi)
Binary
No binary (build failed)
Architecture & Compiler Flags
—
Build Log
(log yok)
Commit Diff GitHub →
docs/busybox.net/developer.html+9 -3
| @@ -13,9 +13,15 @@ will want to add the following to set up your environment: | |
| 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> | |