Re: "svn mv" on non-empty directory --> "WC not locked" or "txn out of date"

I wrote:

> How difficult would the following be? (I'm guessing that the
> answer is "altogether too difficult".) In txn_body_commit,
> before giving up because a txn is out of date, check to see
> whether the two revisions are "the same" (i.e., nothing has
> changed between them). If they aren't, then we report
> SVN_ERR_FS_TXN_OUT_OF_DATE as at present. But
> if they're the same, then we allow everything to go ahead.
>
> We must be able (in principle) to tell whether anything has
> changed, because otherwise "svn status" wouldn't work.
> It naively looks to me as if svn_fs_contents_changed will
> determine this.
>
> Doubtless I'm being *very* naive here. Enlighten me ...

After spending a few minutes digging through the relevant
bits of source, I now think the answer is: yes, I was being very
naive :-).

Oh well. I suppose this has to wait until svn mv becomes
atomic, then.

-- 
g
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org