Re: Partial Checkout feature request.

Sven Brueggemann wrote:
> Hello,
>
> Michael Marcin wrote:
>> /
>> branches/
>> tags/
>> trunk/
>> A/
>> B/
>> C/
>> Where A/ B/ and C/ are each fairly large (say 100MB+)
>> 1/3 of the people at our company need only A/
>> 1/3 of the people need only B/ and C/
>> and the rest need either all of trunk/ or some combination of its
>> children.
>> So the next thing we tried was to have everyone checkout exactly
>> what they needed with several checkouts into the same directory.
>> i.e. they would checkout trunk/B/ and checkout trunk/C/ to c:/trunk.
>> Then highlight all folders in c:/trunk to do updates and commits. This
>> however means that if there is a change to trunk/B/ and trunk/C/ at
>> the same time the revision number is incremented once for each folder
>> they checkout This makes seeing what changed in updates and going back
>> to old versions very difficult.
>
> What about this:
>
> Create a folder D in the repository. It can be empty - I use it to
> store files common to A, B and C.
>
> Check out D to your hard drive (c:\WC} and create the folders for the
> projects you need (say: c:\WC\B and c:\WC\C). Check out trunk/B to
> c:\WC\B and trunk/c to c:\WC\C.
>
> You now have working copies inside a working copy (nested WCs).
>
> You can use c:\WC\B and c:\WC\C like any "normal" working copy. In case
> you need to commit a change that affects both B and C, you can multi-select
> both WCs and commit them together in a single revision. Or do the same
> by selecting "commit" on any WC and drag and drop the changes from the
> other WC to the commit dialog.

That works provided the empty folder and the nested folders are all in
the same repository. Naturally you must be careful to avoid committing
anything to the dummy empty folder, as it will not appear in the
repository at the same level as A, B and C.

The very similar solution using externals (mentioned in the FAQ) needs
the same care.

Simon

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest Interface to (Sub)Version Control
    /_/   \_\     http://tortoisesvn.net
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org