[C++-sig] Re: New indexing suite nearing review readiness

[Raoul Gough]

"Ralf W. Grosse-Kunstleve" <rwgk at yahoo.com> writes:

> --- Joel de Guzman <djowel at softhome.net> wrote:
>> I've never had any problems with branches at all. I see no reason
>> why you can't play with the new indexing suite while sitting on a
>> separate branch.  My main Boost (and Spirit) directory has
>> directories from different branches. When I find a branch stable, I
>> merge it to the head. What "more problems" are you referring to in
>> particular?
>
> Never mind, if you have strong feelings I'll try to adjust.

Well, I'm a bit confused about this branching business. If I create a
branch on the files in (say) boost/python/suite/indexing/ and I then
do a cvs update -r my_new_branch in a parent directory, won't that then
delete all the files that don't *have* a my_new_branch?

[in directory /d/CVS/boost-sandbox/boost-sandbox/boost]

$ cvs update -r indexing_20031006 .
cvs server: Updating .
cvs server: any.hpp is no longer in the repository
cvs server: array_traits.hpp is no longer in the repository
cvs server: assign.hpp is no longer in the repository
cvs server: bigint.hpp is no longer in the repository
cvs server: bigint_gmp.hpp is no longer in the repository
cvs server: bit_reference.hpp is no longer in the repository
cvs server: bit_vector.hpp is no longer in the repository
[etc...]

-- 
Raoul Gough.
(setq dabbrev-case-fold-search nil)