[Please do not mail me a copy of your followup] boost@lists.boost.org spake the secret code <1556602.1zBCzYmS8I@speed> thusly:
The conversion is still in progress. The submodules are still missing from the intended top-level repository.
That explains why I didn't see a .gitmodules file (or whatever it's called) in the top-level repo. I'm familiar with subrepos in mercurial and these sound similar to git's submodules. I was interested in trying it out because I'm overhauling boost.test docs and one of my reviewers was asking about making my source changes available. It seemed that forking boostorg/test and pushing my changes to my fork would be the best way to share these changes, even if I'm jumping into the modular boost fire a little bit. Right now I'm making changes using mercurial patches so I am not in danger of losing changes and I'm getting the benefits of incremental version control, but it's not really shareable. I just cloned boostorg/test last night and I was going to see about pushing my changes into there but I didn't get that far. -- "The Direct3D Graphics Pipeline" free book http://tinyurl.com/d3d-pipeline The Computer Graphics Museum http://computergraphicsmuseum.org The Terminals Wiki http://terminals.classiccmp.org Legalize Adulthood! (my blog) http://legalizeadulthood.wordpress.com