Re: Sparse checkouts suggestion

>
> This is an old idea. If you want to implement it, a file is not the
> right place for the view definition; a property on a directory might be.
>

A Svn property that sets for the user and workspace only, and retains no
history, right? Meaning if the user had two checkouts of the same Svn URL,
then they could maintain two different sparse mappings, right?

That would make it like Perforce's implementation. The perforce commands
for export a client spec, and import again:

p4 client -o > .p4_clientspec_mappings.txt

# modify something

p4 client -i < .p4_clientspec_mappings.txt

Judicious use of this in Google is part of their economic miracle and one
of the dynamics of their scaling Trunk-Based Development to 25,000
developers in one trunk in one repo, with 9 million source files at HEAD
revision :)

- Paul
Received on 2017-09-13 09:26:09 CEST