Changes between Version 1 and Version 2 of ModCvtSvn2Git
- Timestamp:
- Dec 6, 2012, 8:25:47 PM (10 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
ModCvtSvn2Git
v1 v2 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 multiple public Git repositories hosted at [https://github.com GitHub]: 4 4 5 * The public Boost super-modulerepository, with **no history**.6 * A public repository for each Boost library, with **no history**. Each individual Boost library is treated as a separate sub-module by the Boost super-module.5 * The public [https://github.com/boost-lib/boost Super-project for modularized Boost] repository, with **no history**. 6 * A public [https://github.com/boost-lib repository for each Boost library], with **no history**. 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 7 * A public [https://github.com/ryppl/boost-svn Boost history repository], with the **full history** from the old Subversion repository. 8 8 … … 17 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 18 19 Discussion is underway of providing a script to graft on individual library history from fromthe overall history.19 Discussion is underway of providing a script to graft on individual library history from the overall history.