Re: cannot commit property data

On 8/25/06, Ralf Stephan <ralf@ark.in-berlin.de> wrote:

> Why should svn need to get some info back from the server it already
> has? I know I should always svn up before any commit but when you
> are the only committer you don't expect such an error.

Please read chapter 2 in the svn book, 'basic concepts'. In
particular, see the section at the end about mixed revision working
copies. You cannot commit a propchange to a directory unless its
local revision is equal to HEAD. That's one of the only two
restrictions that exist:

http://svnbook.red-bean.com/nightly/en/svn.basic.in-action.html#svn.basic.in-action.mixedrevs

>
> But even if this is my error, it should be clearer what I did wrong,
> e.g., by giving an informative error message like "The server has
> received a directory related commit earlier, and you better do a
> svn up first before committing something to the directory."

Again, if you don't know what the phrase "out of date" means, you
might want to read the 'basic concepts' chapter. It's fundamental
terminology used all over subversion. Users are going to see that
phrase appear when trying to commit files as well.

The error message, I hope, at least says *which* item is out of date.
Does it not?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Aug 27 15:35:21 2006