From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-05-05 22:34:57
----- Original Message -----
From: "Rene Rivera" <grafik666_at_[hidden]>
> OK, that seems reasonable.
> How's this for a todo list:
> * Go through code and patch the " " variables.
OK, but I think this comes after step 3, no? At least, we need to identify
these before trying to patch them.
> * Create a template for documenting the variables for setting up
> It should accomodate both general variables and toolset variables. Dave,
> suggest you do this, you are more familiar with the look-and-feel of
OK, I can do that. BTW, there's no standard look-and-feel. I just plan to
create a gcc-tools.html file. I'll have that checked in by tomorrow
> * Go through code and identify and document each variable that is
> to changing the behaviour of building. We should be able to split this
> among us to get it done faster.
> Given the schedule of branching on the 8th can we get all that done? Or
> we keep adding documentation to the branch after the 8th, and just make
> we have the code changes done?
I was planning this on the basis of the latter assumption.
> By the way... I'll only have about 6 or so hours to spend on this through
> Wednesday. So the sooner we get started the better.
Oof. Let's go!
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk