| | 1 | = Moving Sandbox Libraries to GitHub = |
| | 2 | |
| | 3 | The Boost Sandbox is no longer needed. A proposed Boost library will be hosted publically on the developer's [https://github.com] account instead. |
| | 4 | |
| | 5 | If you have a proposed library in the sandbox, you may want to move it to !GitHub. Here is the procedure I used to move the **endian** sandbox library to !GitHub. |
| | 6 | |
| | 7 | * Create a empty repository named "endian" in my !GitHub account via the usual web interface. |
| | 8 | |
| | 9 | * Run the following from the command line in a temporary directory. |
| | 10 | |
| | 11 | {{{ |
| | 12 | git svn clone http://svn.boost.org/svn/boost/sandbox/endian |
| | 13 | cd endian |
| | 14 | git push --mirror git@github.com:Beman/endian.git |
| | 15 | }}} |
| | 16 | |
| | 17 | * The {{{endian}}} local repository created in the previous steps **must not be used** for actual development because it contains hidden Subversion bridge metadata that interferes with normal Git operations. It can be deleted now or later. Then clone the !GitHub repository in the parent directory where it should live permanently. |
| | 18 | |
| | 19 | {{{ |
| | 20 | cd permanent-parent-directory |
| | 21 | git clone git@github.com:Beman/endian.git |
| | 22 | }}} |
| | 23 | |
| | 24 | |
| | 25 | |
