Changes between Version 6 and Version 7 of ModCvtSvn2Git
- Timestamp:
- Feb 10, 2013, 4:21:44 PM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ModCvtSvn2Git
v6 v7 3 3 As part of the process of moving to modularized Boost, the single Subversion repository at https://svn.boost.org/svn will be converted to multiple public Git repositories hosted at [https://github.com GitHub]: 4 4 5 * The public [https://github.com/boost-lib/boost Super-project for modularized Boost] repository, that at conversion will have **no history**. History will begin to accumulate as changes occur. 6 * A public [https://github.com/boost-lib repository for each Boost library], that at conversion will have **no history**. History will begin to accumulate as changes occur. Each individual Boost library is treated as a separate sub-module by the Boost super-project. The URL for each library's repository is formed by appending the library name to !https://github.com/boost-lib/. For example, https://github.com/boost-lib/algorithm. 7 * A public [https://github.com/ryppl/boost-svn Boost history repository], with the **full history** from the old Subversion repository. 5 * The public [https://github.com/boostorg/boost Super-project for modularized Boost] repository. 6 * A public [https://github.com/boostorg repository for each Boost library]. Each individual Boost library is treated as a separate sub-module by the Boost super-project. The URL for each library's repository is formed by appending the library name to !https://github.com/boostorg/. For example, https://github.com/boostorg/algorithm. 8 7 9 8 == Individual Libraries == 10 9 11 The directory structure of each individual Boost library will be the same as the library's current directory structure under boost-root/libs, except that it will also include a new sub-directory tree {{{include/boost/}}} containing the library's header files. For details, see [StartModDev Getting Started with Modular Boost Library Development using Git].10 The directory structure of each individual Boost library will be the same as the library's current svn boost-root/libs/lib-name directory structure, except that it will also include a new sub-directory tree {{{include/boost/}}} containing the library's header files. For details, see [StartModDev Getting Started with Modular Boost Library Development using Git]. 12 11 13 12 At conversion, each individual Boost library's public repository will contain two branches, {{{master}}}, converted from Subversion {{{branches/release}}}, and {{{develop}}}, converted from {{{trunk}}}. The library maintainer may want to add other branches, as described in [wiki:StartModWorkflow Getting Started with Modular Boost Library Development Workflow]. 14 13 15 == History == 16 17 If the Boost Subversion repository was being converted to a single Subversion repository, the history would just be converted along with everything else. But instead, Boost is being modularized into 120 or so separate repositories. If all history were just blindly included for each library, 233 megs of history would be multiplied by 120 libraries, resulting in a file size of 28 gigs. If you are doing release management or testing, that isn't really acceptable. 18 19 We will provide a Git translation of the monolithic SVN history along with instructions for using the [http://git-scm.com/2010/03/17/replace.html git-replace] command to link it into a modularized repository. 14 The {{{master}}} and {{{develop}}} branches will have full history corresponding to svn history from {{{branches/release}}} and {{{trunk}}} respectively. Information about the history conversion is available [https://github.com/ryppl/boost-svn2git/wiki here]. 20 15 21 16 == Administrative Privileges ==