Re: Request/Proposal for Folder Cloaking -- Second Attempt

Aye, cloaking is one of the features that we miss slightly from our
SOS/VSS migration (although since SOS didn't support it, we rarely used it).

Looking at the linked proposal, I'm wondering if the "depth-immediates"
should be changed to "depth=N", where you could tell SVN how many layers
to delve down when doing the update. So "depth-immediates" would
basically be a "depth=1" (if I understand correctly).

I could see cases where I would specify "depth=2", for instance, when
checking out the root folder of our job tree, which is structured as:

repos-name/A..Z/AW_AcmeWidgets/AW30xx/AW3030_ProjectName

When doing the initial checkout, we'd probably specify a depth of 2 or 3
so that we get everything down to the AW30xx level. Which would be a
very fast update for us since it's only folder structure with few files.

Maybe that idea is already in there, I see depth values of 0 / 1 /
infinity, but not something more generic like 2 / 3 / etc.

...

I'm not entirely sure that the proposal that you linked solves the idea
of cloaked (or "ignored on the client-side") directories / files. In
VSS you could right-click on any file / folder in the GUI explorer,
cloak it, and then it would never get downloaded if you did a "Get
Latest" (or "Recursive Checkout").

Also not sure if it allows "deep / selective" checkouts that are
multiple layers below the current working folder's URL.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Nov 3 20:52:58 2006