On Wed, Dec 14, 2011 at 09:10:56PM -0600, Thomas Dziedzic wrote: > Hi, > > I used to be able to do: > svn checkout --depth=empty svn://svn.archlinux.org/packages > cd packages > svn up pacman > rm -r pacman > svn up > > and it would leave me with an empty, working copy on my computer in > subversion 1.6.17 > > When I upgraded to subversion 1.7.2, after doing the same set of > commands as described above, > the last svn up brings back the pacman folder into the working copy. > > So far, I haven't been able to find any documented proof that this is > an intentional change. > > Finally, when I run: > > svn up --set-depth exclude pacman > > This works as expected. > > So my question is, am I experiencing a regression? Or is this new, > intended behavior with subversion 1.7? > > Thanks for your time!
Removing any .svn directories (e.g. pacman/.svn in your example) has never been a valid use case.
