Re: Directory out-of-date (issue 987)

Ben Collins-Sussman <sussman@collab.net> writes:

> Karl Fogel <kfogel@newton.ch.collab.net> writes:
>
> > Philip Martin <philip@codematters.co.uk> writes:
> > > 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?
> >
> > I think it's merely expediency. If we could be more permissive (while
> > still being correct, of course), that would be better.
>
> Heh, even in the long run, I don't see how we could be more
> permissive. This is exactly the same problem/reason we don't allow
> propchanges on out-of-date directories. Adding/removing items to an
> out-of-date directory is just as illegal.

Not so...

export REPO=http://localhost:8888/repo
svnadmin create repo
svn mkdir $REPO/foo
svn co $REPO wc1
svn co $REPO wc2
svn mkdir wc1/foo/bar1
svn ci wc1
svn mkdir wc2/foo/bar2
svn ci wc2
svn rm wc1/foo/bar1
svn ci wc1

This lets me to create foo/bar2 in wc2, and delete foo/bar1 from wc1,
even though foo is out-of-date in both cases. I can add and delete
items from an out-of-date directory, I cannot however delete the
out-of-date directory or commit propchanges to such a directory. I
think this behaviour is fine, it's just the status display that
strikes me as odd.

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