1234567891011121314151617181920212223242526272829303132333435363738394041424344454647 |
- <!--#include file="header.html" -->
- <h3>Developer Access</h3>
- Because we use Git for version control, you don't need developer (ssh)
- access on uclibc.org to contribute to Buildroot, but you can request
- it if needed.
- <p>
- To obtain developer 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 logging in, 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> It is recommended that
- you generate a key with a "passphrase" for security reasons.
- <p>
- Make the file known to the system by running
- <pre>ssh-add ~/.ssh/id_dsa</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>
- Once you have an account, you can use it to store Git
- repositories. Simply put them in subdirectories of your ~/git, and
- touch ~/git/<repo>/git-daemon-export-ok, after which the hourly
- cronjob will pick them up and show them in cgit. They are also
- available though git-daemon:
- <pre>git clone git://git.buildroot.net/~<USERNAME>/git/<REPO></pre>
- For additional detail on how to use Git, please visit the
- <a href="http://git-scm.org/">the Git website</a>.
- <!--#include file="footer.html" -->
|