[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

cannot commit property data

From: Ralf Stephan <ralf_at_ark.in-berlin.de>
Date: 2006-08-25 16:39:18 CEST

there is one behaviour of subversion which I think is a bug, or
at least, it should be documented in the FAQ and the book, as it
can confuse people a lot. To reproduce:

1. check out a fresh copy of any repo
2. change something in a directory, i.e., svn add file
3. svn ci file
4. svn propedit svn:ignore . (the same directory you changed in 2)
5. svn ci .
Output: Commit failed. Out of date.
    Comment: I know it's not correct but it happened to me when I knew
    exactly that noone else had committed between 3 and 5.

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.

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."

And even if that is not possible then this case should be handled in
the book and the FAQ. Why? Because I'm not the first to get bitten
by it:


So please, people, do something such that the next victim of this
misdesign will not sit there and, like me, ask himself "What was
wrong with that?"

Thanks for your time,


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Aug 27 14:26:52 2006

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.