Hi Stefan,
Thanks for the explanation - I always forget about the subtleties of using
-r versus @. I now understand what Subversion is doing here and why,
but I maintain that it should give some indication that the workspace is not
pointing at the "expected" repository location. Yes, it's the res
On Sun, May 11, 2014 at 07:10:47PM +1200, Fergus Slorach wrote:
>
> Checking out a copied directory at a revision prior to the copy results in
> a checkout of the data before the copy. I would expect this to fail in the
> same way that attempting to update to an invalid revision fails.
> Is this t
Checking out a copied directory at a revision prior to the copy results in
a checkout of the data before the copy. I would expect this to fail in the
same way that attempting to update to an invalid revision fails.
Is this the intended behaviour? If so, shouldn't there be some message that
your w
