diff --git a/docs/buildroot.html b/docs/buildroot.html index 09136aefe5..a79cd4ad42 100644 --- a/docs/buildroot.html +++ b/docs/buildroot.html @@ -119,7 +119,7 @@

Obtaining Buildroot

Buildroot releases are made approximately every 3 - months. Direct SVN access and daily SVN snapshots are also + months. Direct Git access and daily snapshots are also available if you want more bleeding edge.

Releases are available at http://buildroot.net/downloads/snapshots/.

-

To download Buildroot using SVN, you can simply follow - the rules described on the "Accessing SVN"-page (http://buildroot.net/subversion.html) +

To download Buildroot using Git, you can simply follow + the rules described on the "Accessing Git"-page (http://buildroot.net/git.html) of the Buildroot website (http://buildroot.net), and download the - buildroot SVN module. For the impatient, here's a quick + "http://buildroot.net">http://buildroot.net), and download + buildroot from Git. For the impatient, here's a quick recipe:

- $ svn co svn://uclibc.org/trunk/buildroot
+ $ git clone git://git.buildroot.net/buildroot

Using Buildroot

@@ -515,7 +515,7 @@ $ make me<TAB> uncompress the target/generic/skel.tar.gz file to create the main subdirectories and symlinks, copies the skeleton available in target/generic/target_skeleton and then removes useless - .svn/ directories. + .svn/CVS directories.
  • Add the TARGETS dependency. This should generally check if the configuration option for this package is enabled, and if so then diff --git a/docs/developer.html b/docs/developer.html index d25e02cdcf..ee83324d5d 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. diff --git a/docs/download.html b/docs/download.html index 6640aafd01..ec2cf56e0a 100644 --- a/docs/download.html +++ b/docs/download.html @@ -13,7 +13,7 @@ The latest release can always be dowloaded from You can also obtain Daily Snapshots of the latest Buildroot source tree if you want to to -follow development, but cannot or do not wish to use Subversion (svn). +follow development, but cannot or do not wish to use Git. diff --git a/docs/git.html b/docs/git.html new file mode 100644 index 0000000000..ef20eeaa64 --- /dev/null +++ b/docs/git.html @@ -0,0 +1,38 @@ + + + +

    Git Access

    + +The buildroot repository can be browsed online through cgit at +http://git.buildroot.net/buildroot. +To grab a copy of the repository use + +
    +git clone git://git.buildroot.net/buildroot
    + +Or if you're behind a firewall blocking git: + +
    +git clone http://git.buildroot.net/buildroot
    + +

    + +If you are not already familiar with using Git, we recommend you visit the Git website. + +

    + +Once you've checked out a copy of the source tree, you can update your source +tree at any time so it is in sync with the latest and greatest by entering your +buildroot directory and running the command: + +

    +git pull
    + +Because you've only been granted anonymous access to the tree, you won't be +able to commit any changes. Changes can be submitted for inclusion by posting +them to the buildroot mailing list or to the Bug and Patch Tracking System. + + + diff --git a/docs/header.html b/docs/header.html index 9698adf471..c9e5817323 100644 --- a/docs/header.html +++ b/docs/header.html @@ -34,8 +34,8 @@
    About
    Latest News
    Download -
    Browse Source -
    Accessing Source +
    Browse Source +
    Accessing Source
    Bug Tracking
    Documentation
    Mailing Lists diff --git a/docs/news.html b/docs/news.html index d8117cc093..033dee1eb6 100644 --- a/docs/news.html +++ b/docs/news.html @@ -6,6 +6,17 @@