| | 1 | = Conversion of the Subversion repository to Git public repositories = |
| | 2 | |
| | 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 | |
| | 5 | * The public Boost super-module repository, 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. |
| | 7 | * A public [https://github.com/ryppl/boost-svn Boost history repository], with the **full history** from the old Subversion repository. |
| | 8 | |
| | 9 | == Individual Libraries == |
| | 10 | |
| | 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. |
| | 12 | |
| | 13 | Each individual Boost library's public repository will contain a single branch, "master", that corresponds to {{{branches/release}}} in Subversion. |
| | 14 | |
| | 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 | Discussion is underway of providing a script to graft on individual library history from from the overall history. |
