Invalid change ordering?

[Dirk]

>
> Ref the branch handler... ideally, when (say) BAAAAAAA is branched at 
> revision 3 to create GAAAAAAA, the internal state tracking GAAAAAAA's 
> parent paths would inherit BAAAAAAA's up to revision 3. Then if 
> GAAAAAAA is shared elsewhere and then branched or pinned to revision 1 
> or 2, it knows where to get this...
Should be fixed in [298]. The code will query the ancestor for a valid 
path and the copy from that one.

Dirk