Re: Commit bug?

Greg Stein <gstein@lyra.org> writes:

> As Ben said. There is a bug with directory properties. Update first (even if
> you're the only person working on the repository). Then commit.

Whoa thar, I never said it was a bug. It's a very deliberate decision,
even documented in doc/user/manual/dirversioning.texi.

Imagine you have revision 7 of directory FOO in your working copy.
Now you add some props to FOO and commit, thereby creating revision 9.

Why revision 9? Because unbeknownst to you, somebody added a new file
(BAR) to the directory in revision 8.

Of course, after you did your property commit, your working revision
number on FOO was bumped to 9. (You created 9, after all.) Now
whenever you do an update, you will *never* get that file added in
revision 8. The server thinks you already have it!

This is why we insist on directories being up-to-date when committing
properties on them. Any commit will cause the committed item's
working revision to be "bumped", but in this case the bump could bring
about bad results. We need to make certain guarantees that when a
working copy directory is at version X, it actually has the same list
of entries (ignoring add/delete schedulings) as DIR:X on the server.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:37:01 2006