[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Re: Merging and Sparse Checkouts

From: SIDOS Joel <JSIDOS_at_cegid.fr>
Date: Fri, 17 Oct 2008 14:56:33 +0200

Thanks for your answers.
Unfortunately, your answer about my "externals" question seems not working.
I tried the extraction with "immediate children, including folders" with 2 differents clients :
- which is our production version
- for test
The result is the same in those two cases :
        MyBranch (immediate children, including folders)
        |_ Rep1 (empty)
        |_ Rep2 (empty)
But no external subdirectories.


-----Message d'origine-----
De : Stefan Küng [mailto:tortoisesvn_at_gmail.com]
Envoyé : vendredi 17 octobre 2008 13:09
À : users_at_tortoisesvn.tigris.org
Objet : Re: Merging and Sparse Checkouts

SIDOS Joel wrote:
> I agree with you about the "working copy" depth.
> Also, I try to merge with the "Fully Recursive" option.
> But my problem is : "the test merge" interface doesn't give my same results than the real merge operation.
> The "real merge operation" seems to be ok, but the "test merge" gives
> me some Is this problem known ?

Yes. See, the test merge doesn't actually do the merge, so it has to do a lot of guessing about the merge outcome, and that guessing is not always a 100% accurate.

> Second question please : how can I have a working copy with sparse checkout subdirectories and all my externals ?
> I would obtain :
> MyBranch (Only this item) (Mybranche has svn:externals with External1 ... External2)
> |_ Rep1 (Fully recursive)
> |_ External 1
> |_ External 2

checkout MyBranch with "immediate children, including folders".
Otherwise you won't get the externals.


  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net
Received on 2008-10-17 14:58:49 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.