Hi all,
We make very heavy use of sparse checkouts. They're absolutely key for us, as
our product consists of many directories, only a handful of which will actually
change on any given branch. A complete working copy is too large and unwieldy
to deal with - checking out takes hours, and any op
You can easily check for sparse checkouts by running svnversion:
If the reported version has a P attached, then you have a sparse
checkout.
I have similar problems with unwanted sparse checkouts esp. when it
comes to merging.
Thanks for the hints in this thread about the potential bug origins.
-
