Loading docs/buildroot.html +8 −8 Original line number Diff line number Diff line Loading @@ -119,7 +119,7 @@ <h2><a name="download" id="download"></a>Obtaining Buildroot</h2> <p>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.</p> <p>Releases are available at <a Loading @@ -130,16 +130,16 @@ and previous snapshots are also available at <a href="http://buildroot.net/downloads/snapshots/">http://buildroot.net/downloads/snapshots/</a>. </p> <p>To download Buildroot using SVN, you can simply follow the rules described on the "Accessing SVN"-page (<a href= "http://buildroot.net/subversion.html">http://buildroot.net/subversion.html</a>) <p>To download Buildroot using Git, you can simply follow the rules described on the "Accessing Git"-page (<a href= "http://buildroot.net/git.html">http://buildroot.net/git.html</a>) of the Buildroot website (<a href= "http://buildroot.net">http://buildroot.net</a>), and download the <code>buildroot</code> SVN module. For the impatient, here's a quick "http://buildroot.net">http://buildroot.net</a>), and download <code>buildroot</code> from Git. For the impatient, here's a quick recipe:</p> <pre> $ svn co svn://uclibc.org/trunk/buildroot $ git clone git://git.buildroot.net/buildroot </pre> <h2><a name="using" id="using"></a>Using Buildroot</h2> Loading Loading @@ -515,7 +515,7 @@ $ make me<TAB> uncompress the <code>target/generic/skel.tar.gz</code> file to create the main subdirectories and symlinks, copies the skeleton available in <code>target/generic/target_skeleton</code> and then removes useless <code>.svn/</code> directories. </li> <code>.svn/CVS</code> directories. </li> <li>Add the <code>TARGETS</code> dependency. This should generally check if the configuration option for this package is enabled, and if so then Loading docs/developer.html +24 −42 Original line number Diff line number Diff line <!--#include file="header.html" --> <h3>Subversion Read/Write Access</h3> <h3>Developer 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:buildroot@uclibc.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. <p> 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 /home/<USERNAME>/.ssh/id_dsa.pub</pre> 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 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 Loading @@ -32,33 +31,16 @@ The content of 'id_dsa' should of course be kept secret. <p> 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: <pre> svn list svn+ssh://username@svn.uclibc.org/svn/trunk/buildroot</pre> <br> It goes without saying you must change <em>username</em> to your own username... <p> 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: <pre> svn diff svn status svn revert svn commit</pre> <p> 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" --> Loading docs/download.html +2 −7 Original line number Diff line number Diff line Loading @@ -13,7 +13,7 @@ The latest release can always be dowloaded from You can also obtain <a href="/downloads/snapshots/">Daily Snapshots</a> 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. <ul> <li> Click here to <a href="downloads/snapshots/">Daily Snapshots</a>. Loading @@ -22,13 +22,8 @@ follow development, but cannot or do not wish to use Subversion (svn). <li> Click here to <a href="http://sources.busybox.net/index.py/trunk/buildroot/">browse the source tree</a>. </li> <li>Anonymous <a href="subversion.html">Subversion access</a> is available. <li>Anonymous <a href="git.html">Git access</a> is available. </li> <li>For those that are actively contributing obtaining <a href="developer.html">Subversion read/write access</a> is also possible. </li> </ul> <!--#include file="footer.html" --> Loading docs/subversion.html→docs/git.html +38 −0 Original line number Diff line number Diff line <!--#include file="header.html" --> <h3>Anonymous Subversion Access</h3> <h3>Git Access</h3> We allow anonymous (read-only) Subversion (svn) access to everyone. To grab a copy of the latest version of buildroot using anonymous svn access: The buildroot repository can be browsed online through cgit at <a href="http://git.buildroot.net/buildroot">http://git.buildroot.net/buildroot</a>. To grab a copy of the repository use <pre> svn co svn://uclibc.org/trunk/buildroot</pre> git clone git://git.buildroot.net/buildroot</pre> Or if you're behind a firewall blocking git: <pre> git clone http://git.buildroot.net/buildroot</pre> <p> If you are not already familiar with using Subversion, I recommend you visit <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>. If you are already comfortable with using CVS, you may want to skip ahead to the <a href="http://svnbook.red-bean.com/en/1.1/apa.html">Subversion for CVS Users</a> part of the Subversion Book. If you are not already familiar with using Git, we recommend you visit <a href="http://git-scm.org">the Git website</a>. <p> Loading @@ -27,14 +27,12 @@ tree at any time so it is in sync with the latest and greatest by entering your buildroot directory and running the command: <pre> svn update</pre> git pull</pre> 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 <a href="http://bugs.uclibc.org/">Bug and Patch Tracking System</a>. For those that are actively contributing <a href="developer.html">Subversion commit access</a> can be made available. <!--#include file="footer.html" --> docs/header.html +2 −2 Original line number Diff line number Diff line Loading @@ -34,8 +34,8 @@ <br><a href="/about.html">About</a> <br><a href="/news.html">Latest News</a> <br><a href="/download.html">Download</a> <br><a href="http://sources.busybox.net/index.py/trunk/buildroot/">Browse Source</a> <br><a href="/subversion.html">Accessing Source</a> <br><a href="http://git.buildroot.net/buildroot">Browse Source</a> <br><a href="/git.html">Accessing Source</a> <br><a href="http://bugs.uclibc.org/">Bug Tracking</a> <br><a href="/docs.html">Documentation</a> <br><a href="/lists.html">Mailing Lists</a> Loading Loading
docs/buildroot.html +8 −8 Original line number Diff line number Diff line Loading @@ -119,7 +119,7 @@ <h2><a name="download" id="download"></a>Obtaining Buildroot</h2> <p>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.</p> <p>Releases are available at <a Loading @@ -130,16 +130,16 @@ and previous snapshots are also available at <a href="http://buildroot.net/downloads/snapshots/">http://buildroot.net/downloads/snapshots/</a>. </p> <p>To download Buildroot using SVN, you can simply follow the rules described on the "Accessing SVN"-page (<a href= "http://buildroot.net/subversion.html">http://buildroot.net/subversion.html</a>) <p>To download Buildroot using Git, you can simply follow the rules described on the "Accessing Git"-page (<a href= "http://buildroot.net/git.html">http://buildroot.net/git.html</a>) of the Buildroot website (<a href= "http://buildroot.net">http://buildroot.net</a>), and download the <code>buildroot</code> SVN module. For the impatient, here's a quick "http://buildroot.net">http://buildroot.net</a>), and download <code>buildroot</code> from Git. For the impatient, here's a quick recipe:</p> <pre> $ svn co svn://uclibc.org/trunk/buildroot $ git clone git://git.buildroot.net/buildroot </pre> <h2><a name="using" id="using"></a>Using Buildroot</h2> Loading Loading @@ -515,7 +515,7 @@ $ make me<TAB> uncompress the <code>target/generic/skel.tar.gz</code> file to create the main subdirectories and symlinks, copies the skeleton available in <code>target/generic/target_skeleton</code> and then removes useless <code>.svn/</code> directories. </li> <code>.svn/CVS</code> directories. </li> <li>Add the <code>TARGETS</code> dependency. This should generally check if the configuration option for this package is enabled, and if so then Loading
docs/developer.html +24 −42 Original line number Diff line number Diff line <!--#include file="header.html" --> <h3>Subversion Read/Write Access</h3> <h3>Developer 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:buildroot@uclibc.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. <p> 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 /home/<USERNAME>/.ssh/id_dsa.pub</pre> 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 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 Loading @@ -32,33 +31,16 @@ The content of 'id_dsa' should of course be kept secret. <p> 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: <pre> svn list svn+ssh://username@svn.uclibc.org/svn/trunk/buildroot</pre> <br> It goes without saying you must change <em>username</em> to your own username... <p> 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: <pre> svn diff svn status svn revert svn commit</pre> <p> 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" --> Loading
docs/download.html +2 −7 Original line number Diff line number Diff line Loading @@ -13,7 +13,7 @@ The latest release can always be dowloaded from You can also obtain <a href="/downloads/snapshots/">Daily Snapshots</a> 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. <ul> <li> Click here to <a href="downloads/snapshots/">Daily Snapshots</a>. Loading @@ -22,13 +22,8 @@ follow development, but cannot or do not wish to use Subversion (svn). <li> Click here to <a href="http://sources.busybox.net/index.py/trunk/buildroot/">browse the source tree</a>. </li> <li>Anonymous <a href="subversion.html">Subversion access</a> is available. <li>Anonymous <a href="git.html">Git access</a> is available. </li> <li>For those that are actively contributing obtaining <a href="developer.html">Subversion read/write access</a> is also possible. </li> </ul> <!--#include file="footer.html" --> Loading
docs/subversion.html→docs/git.html +38 −0 Original line number Diff line number Diff line <!--#include file="header.html" --> <h3>Anonymous Subversion Access</h3> <h3>Git Access</h3> We allow anonymous (read-only) Subversion (svn) access to everyone. To grab a copy of the latest version of buildroot using anonymous svn access: The buildroot repository can be browsed online through cgit at <a href="http://git.buildroot.net/buildroot">http://git.buildroot.net/buildroot</a>. To grab a copy of the repository use <pre> svn co svn://uclibc.org/trunk/buildroot</pre> git clone git://git.buildroot.net/buildroot</pre> Or if you're behind a firewall blocking git: <pre> git clone http://git.buildroot.net/buildroot</pre> <p> If you are not already familiar with using Subversion, I recommend you visit <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>. If you are already comfortable with using CVS, you may want to skip ahead to the <a href="http://svnbook.red-bean.com/en/1.1/apa.html">Subversion for CVS Users</a> part of the Subversion Book. If you are not already familiar with using Git, we recommend you visit <a href="http://git-scm.org">the Git website</a>. <p> Loading @@ -27,14 +27,12 @@ tree at any time so it is in sync with the latest and greatest by entering your buildroot directory and running the command: <pre> svn update</pre> git pull</pre> 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 <a href="http://bugs.uclibc.org/">Bug and Patch Tracking System</a>. For those that are actively contributing <a href="developer.html">Subversion commit access</a> can be made available. <!--#include file="footer.html" -->
docs/header.html +2 −2 Original line number Diff line number Diff line Loading @@ -34,8 +34,8 @@ <br><a href="/about.html">About</a> <br><a href="/news.html">Latest News</a> <br><a href="/download.html">Download</a> <br><a href="http://sources.busybox.net/index.py/trunk/buildroot/">Browse Source</a> <br><a href="/subversion.html">Accessing Source</a> <br><a href="http://git.buildroot.net/buildroot">Browse Source</a> <br><a href="/git.html">Accessing Source</a> <br><a href="http://bugs.uclibc.org/">Bug Tracking</a> <br><a href="/docs.html">Documentation</a> <br><a href="/lists.html">Mailing Lists</a> Loading