Directory out-of-date (issue 987)

Hello

Consider this script

export REPO=file://`pwd`/repo
rm -rf repo wc
svnadmin create repo
svn co $REPO wc
svn mkdir wc/dir1
svn ci wc
svn st -uv wc
svn mkdir wc/dir1/dir2
svn ci wc
svn st -uv wc

After the first commit the status shows

                0 0 ? wc
                1 1 pm wc/dir1

and after the second commit the status shows

                0 0 ? wc
                1 1 pm wc/dir1
                2 2 pm wc/dir1/dir2

so clearly the post-commit processing is not bumping the parent
directory's revision. I think this is the correct behaviour. It is
possible that the repository version of the parent's directory has
additional items not present in this working copy, so bumping the
revision would be wrong.

The status command queries the repository and the status editor uses
the addition or deletion of items to determine whether a directory is
out of date. In this case there ar no such changes, so the
directories do not show up as out of date.

Now delete dir1 and try to commit, and the commit fails with

svn: out of date: `dir1' in txn `5'

because the revision we are trying to delete is not HEAD.

So to my question:

Is it reasonable for 'svn commit' to fail with an out-of-date message
when 'svn status' doesn't show any out-of-date markers?

We could change 'svn status' so that it always shows out-of-date
markers for directories that are not HEAD, but that is probably a
retrograde step, as we lose the current information about whether
there really are new items or not. We could display some other
out-of-date indicator, i.e. not '*', in this situation. Or we could
accept that the revision numbers themselves are enough. What do
people think?

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