2010-10-26 04:54 AEST by Glen Starrett - Server version 2.5.03 (Scorpio) Build 3804

After setting up Shadow, the first commit was a file to a deep directory within
the structure.  Shadow ran but only updated the deep directory and below -- it
didn't pull the entire structure.

For a shadow entry like this:
^BFooB_H1	 HEAD		E:/Data/Protect/FooFooControl/Auto_Checkout/BFooB_H1


This is run when committing to a deep directory within that module:
16:14:48: S -> CreateProcess(,"C:\Program Files\CVS Suite\CVSNT\cvs.exe" -q -d
E:/Data/CVS/cvsrepo co -R -d
E:/Data/Protect/FooFooControl/Auto_Checkout/BFooB_H1 -r HEAD
BFooB_H1/panels/mcr/barbaz_xy_sdi)

POSSIBLE WORKAROUNDS:
-- Tag a file at the top of the module
-- Commit a change to a file at the top of the module
-- Navigate to the shadow directory on the server and update (cvs up -dP)


Not sure if changing the code to CO the entire module every time would be a good
idea -- performance would take a large hit for large modules, but it's local so
it shouldn't be too bad.

Another idea is that if the shadow directory doesn't exist, then do strip off
the "depth" of the module and then perform the "full" CO.  E.g. in this case,
because "E:/Data/Protect/FooFooControl/Auto_Checkout/BFooB_H1" didn't exist,
change the CO module to the highest level **that still matches the REGEX**.  In
this case from "BFooB_H1/panels/mcr/barbaz_xy_sdi" to "BFooB_H1".