Re: Working copy is not up-to-date. Error?

andreas.koenig@anima.de (Andreas J. Koenig) writes:

> svn co http://..../svn/foo
> svn add bar bar/memo plan.txt
> svn commit -m 'Initial Checkin'
> svn propset svn:ignore "RCS" .
> svn commit -m 'Setting svn:ignore on RCS'

You cannot commit a propchange unless a directory is up-to-date.
That's a restriction that has always existed.

Subversion allows mixed working copies, just like cvs. If you commit
3 items, then after the commit, those 3 items are a newer revision
than the rest of your working copy. This is a feature, not a bug.
:-) It would be a *very* bad thing if every commit forced you to
absorb changes from the server. It just so happens that in a few edge
cases, directories have to be up-to-date to perform certain actions.
One of those edge cases is commiting a directory-property, and another
edge case is removing a directory.

If you want to know exactly why these edge cases are disallowed, take
a look at doc/book/misc-docs/directory_versioning.xml.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Nov 24 15:22:03 2002