I'll do it, now that the release is out.
On 11/19/2013 05:12 AM, Beman Dawes wrote:
> Presumably there are two ways to handle this:
> Option 1: Using svn, merge tools/build trunk to branches/release.
> Option 2: Using git, merge tools/build develop to master, and update boost
> super-project to point to the updated tools/build master branch.
> Who is planning to handle this? Steven?
The merge is non-trivial, since there are some
> Which option do you prefer?
changesets that span other libraries. I'd
I'd much rather do this in svn, since I know