On 5/26/2011 2:17 PM, Stefan Küng wrote:
> On 26.05.2011 18:43, Glenn Carr wrote:
>> I typically go through this process when I'm checking out our code
>> where I start at the top level, get immediate children, drill down
>> thru a subset of those directories, get immediate children, then
>> eventually get the trunk and a couple of other release branches
>> It's not a big deal, just a bit tedious, and I could script this for
>> my particular situation.
>> But, how about if a dialog presented a tree view of the current
>> repository, which a checkbox beside each folder. The checkbox would
>> indicate that I wanted to set the update depth for that folder
>> recursively. No checkbox would indicate to exclude that folder.
> How about this?
That is extremely nice. Yet another reason to look forward to 1.7. Can
that be used to prune a working copy back down, getting rid of
folders/files that we no longer want locally?
We make heavy use of sparse checkouts and while the core users were able
to maintain their sparse working copies, the UI was never that
intuitive. Such as using "Update item to revision" dialog in order to
prune a folder back out of the working copy. It wasn't worth
complaining about at the time because we were just so glad that sparse
checkouts were possible in the first place.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2011-05-26 22:51:32 CEST