Invalid change ordering?

[Dirk]

>>
> Even if an item is deleted, surely it is still a valid source for the 
> revisions of the file to date... i.e. until the file is next updated, 
> it would presumably continue to be a valid share source for the 
> current revision of the file.
>
> Isn't that how a delete/recover cycle works too?
>
Yes, the file is still available up to the revision where it is deleted. 
And this is also the way how a recover is implemented.

But

1.) You can not do a delete and a copy-from the same revision in one 
revision
2.) This case was a share, and a share should copy the "last active" 
path. and the deleted one is definitely no active anymore.

VSS does not record the physical id from the share source. Only the VSS 
path is stored and this is a very fragile information, so we don't 
depend on it. We are talking about the active pathes. And in complex 
share scenarios it could be possible that we copy from a different path 
than the one used in the "original" VSS. But as long as we get the last 
known version number we don't care about this. Another possibility would 
be to never "copy-from" but to always commit the last known version. But 
even if the share source is not 100% correct in all cases, it holds some 
information, since the history of the item is maintained.

Best regards
Dirk