Changes between Version 1 and Version 2 of ExtractSandbox


Ignore:
Timestamp:
Dec 13, 2012, 4:49:59 PM (10 years ago)
Author:
Beman Dawes
Comment:

Add Possible Enhancements, refine other text

Legend:

Unmodified
Added
Removed
Modified

  • ExtractSandbox

    v1 v2  
    11= Moving Sandbox Libraries to GitHub =
    22
    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.
     3The Boost Sandbox is no longer needed since a proposed Boost library can be hosted publicly by the developer's [https://github.com] account.
    44
    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.
     5If you have a proposed library in the sandbox, you may want to move it to !GitHub.
     6
     7== Basic Procedure ==
     8
     9Here is the procedure I used to move the **endian** library from the sandbox to !GitHub. I've simplified it a bit and rerun it several times to verify that it works!
    610
    711* Create a empty repository named "endian" in my !GitHub account via the usual web interface.
    … …  
    1519}}}
    1620
    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.
     21* 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 into the parent directory where it should live permanently.
    1822
    1923{{{
    … …  
    2226}}}
    2327
     28== Possible Enhancements ==
    2429
     30* By default, the history commit messages have a cross-reference to the Subversion revision number. That can be suppressed by adding option {{{--no-metadata}}} like this: {{{git svn clone --no-metadata http://svn.boost.org/svn/boost/sandbox/endian}}}. I actually like the cross-references, so did not use this option.
    2531
     32* Subversion login names can be converted to email addresses. See {{{git svn clone -A}}} option. I found this troublesome, and didn't get it to work, so gave up on it.   
     33