Hi, > Von: Markus Schaber [mailto:m.scha...@3s-software.com] > One current problem is that the revert command refuses to work on a copied > directory with a depth different to infinity. This seems to be issue > 3851[3]. There is written that "in most (all?) cases the user can use > depth=infinity as an alternative".
I think I now found a case where depth=infinity is not an alternative. Assume we are in a working copy, and have a non-modified directory tree foo: -- snip -- m.schaber@SCHABERM /cygdrive/d/testcheckout $ svn cp foo bar A bar m.schaber@SCHABERM /cygdrive/d/testcheckout $ svn status A + bar m.schaber@SCHABERM /cygdrive/d/testcheckout $ touch bar/testfile m.schaber@SCHABERM /cygdrive/d/testcheckout $ svn status A + bar ? bar/testfile m.schaber@SCHABERM /cygdrive/d/testcheckout $ svn propset svn:ignore testfile bar property 'svn:ignore' set on 'bar' m.schaber@SCHABERM /cygdrive/d/testcheckout $ svn status A + bar m.schaber@SCHABERM /cygdrive/d/testcheckout $ svn revert --depth=empty bar svn: Try 'svn revert --depth infinity' instead? svn: Unable to lock 'bar/innerdir' -- snap -- Now, if we have other modifications inside bar, there is no way to revert the change of the svn:ignore property without side effects. Is there a workaround for this situation (working with the API of libsvn 1.6.16)? Maybe manually synchronizing the properties to the BASE state? I'm just starting to look into svn:ignore support, and this problem might hit me sooner or later. Regards, Markus
