|author||Peter Korsgaard <email@example.com>||2009-05-03 22:11:33 +0200|
|committer||Peter Korsgaard <firstname.lastname@example.org>||2009-05-03 22:11:33 +0200|
docs/: announce move to git
Signed-off-by: Peter Korsgaard <email@example.com>
Diffstat (limited to 'docs/developer.html')
1 files changed, 24 insertions, 42 deletions
diff --git a/docs/developer.html b/docs/developer.html
index d25e02cdcf..ee83324d5d 100644
@@ -1,64 +1,46 @@
<!--#include file="header.html" -->
-<h3>Subversion Read/Write Access</h3>
-If you want to be able to commit things to Subversion, first contribute some
-stuff to show you are serious. Then, very nicely ask <a
-href="mailto:firstname.lastname@example.org">The Buildroot Developers</a> to set you up
-with commit access to the Subversion repository. To access Subversion, you
-will want to add the following to set up your environment:
+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.
-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 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
-It is recommended that you generate a key with a "passphrase" for security reasons.
+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
+/home/<USERNAME>/.ssh/id_dsa.pub</pre> It is recommended that
+you generate a key with a "passphrase" for security reasons.
Make the file known to the system by running
-You must then send the content of 'id_dsa.pub' to me so I can setup your account.
+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.
-Once you are setup with an account, you will need to use your account to
-checkout a copy of buildroot from Subversion:
+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:
-svn list svn+ssh://email@example.com/svn/trunk/buildroot</pre>
-It goes without saying you must change <em>username</em> to your own
-You can then enter the newly checked out buildroot directory, make changes, check
-your changes, diff your changes, revert your changes, and and commit your
-changes usine commands such as:
-For additional detail on how to use Subversion, please visit the
-<a href="http://subversion.tigris.org/">the Subversion website</a>.
-You might also want to read online or buy a copy of <a
-href="http://svnbook.red-bean.com/">the Subversion Book</a>...
+<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" -->