on Sun Aug 28 2011, "Niall Douglas" wrote:
> On 27 Aug 2011 at 12:29, Dave Abrahams wrote:
>
>> In that case, if I were you, I would actually start using Git with the
>> modularized / CMake-ified Boost at http://github.com/boost-lib.
>
> If you do go for git, I have found repo embedded per-branc
To summarize how I'm approaching this now:
- I think the cmake/github Boost repositories look like the right place
to put this.
- I'm going to spend some time digesting the langbinding and luabind
code, and try to put together a skeleton package; when it gets mature
enough for others to find
On 27 Aug 2011 at 12:29, Dave Abrahams wrote:
> In that case, if I were you, I would actually start using Git with the
> modularized / CMake-ified Boost at http://github.com/boost-lib.
If you do go for git, I have found repo embedded per-branch issue
tracking (e.g. http://bugseverywhere.org/) to
on Fri Aug 26 2011, Jim Bosch wrote:
> In the interest of keeping this discussion easy-to-follow, I'm going
> to reply to Dave's email twice, with new subjects - I'll stick to
> questions about logistics in this email, and talk about features and
> scope in another.
>
> In summary, I'm getting t
In the interest of keeping this discussion easy-to-follow, I'm going to
reply to Dave's email twice, with new subjects - I'll stick to questions
about logistics in this email, and talk about features and scope in another.
In summary, I'm getting the sense that a branch in the mainline (not
san
