$include_dir="/home/hyper-archives/boost/include"; include("$include_dir/msg-header.inc") ?>
From: jsiek_at_[hidden]
Date: 2000-07-24 20:01:56
Isn't branching the solution to this problem?
Also, we should have a convention for tag names for
boost releases/branches/etc.
For the main line, how about:
boost-1-16-1 (for the current release 1.16.1)
For branches, how about use the name of the new library:
iterator-adaptors
pattern-matching
This also has the advantage that changes needed to common
files like config.hpp can be made and the revision history
will be appropriately recorded.
Cheers,
Jeremy
David Abrahams writes:
> The problem:
>
> How to allow development of new, as-yet-unaccepted libraries without
> "infecting" the main CVS release trunk.