Re: bug

Michael Price <mprice@atl.lmco.com> writes:

> Philip Martin writes:
> > When one commits an item (a file or sub-directory) in an otherwise
> > unchanged directory, the version of that directory in the working copy
> > does not change, and so it becomes out-of-date with respect to the
> > repository. One may add an item to an out-of-date directory, provided
> > it does not conflict with an item in HEAD, and one may delete an item
> > from an out-of-date directory provided the deleted item is up-to-date.
> > One cannot delete, or set properties on, an out-of-date directory.
>
> Oh. So the correct way to do what I wanted was to copy/update/delete
> rather than move (which is just copy/delete).

Well, you have to run update before committing, but exactly when you
do it is up to you.

As you other mail indicates the out-of-date detection doesn't always
work, I've rasied issue 1017. Also, looking at the code it appears
that in the some places where out-of-date detection "works" it's not
reliable (see the issue for details) so we may need to rework this
feature.

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