From e2cac48876e11a29fd7b873dbfe2e5b0138e3fe5 Mon Sep 17 00:00:00 2001 From: Peter Korsgaard Date: Sun, 3 May 2009 22:11:33 +0200 Subject: docs/: announce move to git Signed-off-by: Peter Korsgaard --- docs/developer.html | 66 +++++++++++++++++++---------------------------------- 1 file changed, 24 insertions(+), 42 deletions(-) (limited to 'docs/developer.html') diff --git a/docs/developer.html b/docs/developer.html index d25e02cdc..ee83324d5 100644 --- a/docs/developer.html +++ b/docs/developer.html @@ -1,64 +1,46 @@ -

Subversion Read/Write Access

+

Developer Access

-If you want to be able to commit things to Subversion, first contribute some -stuff to show you are serious. Then, very nicely ask The Buildroot Developers 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

ssh-keygen -t dsa
This will -create the files 
/home/<USERNAME>/ssh/id_dsa
-/home/<USERNAME>/.ssh/id_dsa.pub
-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
ssh-keygen -t dsa
This will create the +files 
/home/<USERNAME>/ssh/id_dsa
+/home/<USERNAME>/.ssh/id_dsa.pub
It is recommended that +you generate a key with a "passphrase" for security reasons.

Make the file known to the system by running 

ssh-add ~/.ssh/id_dsa
-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//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://username@svn.uclibc.org/svn/trunk/buildroot
-
-It goes without saying you must change username to your own -username... -

- -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: - -

-svn diff
-svn status
-svn revert
-svn commit
- -

- -For additional detail on how to use Subversion, please visit the -the Subversion website. -You might also want to read online or buy a copy of the Subversion Book... +

git clone git://git.buildroot.net/~<USERNAME>/git/<REPO>
+For additional detail on how to use Git, please visit the +the Git website. -- cgit v1.2.3