Re: Support for: Setting property on non-local target

[Lieven Govaerts]
> Shouldn't that fail the commit then, like it does for outdated files?
> Or do we need a working copy to get that error?

The whole point here is that, if you operate directly on the
repository, the client has no idea whether or not you have a working
copy that is up to date. It has no way of knowing whether you last
looked at r1 or r2 of a file.

By forcing you to use a working copy for this, the client also knows
whether your wc is up to date when you try to commit.