Re: During sparse checkout, what's the difference between "svn update --depth" and "svn update --set-depth"?
Hi, This is because the existing depth setting is stored in the working copy 'svn info' should reveal this information and doing subsequent update is based on this setting, to modify this --set-depth is required. Best Regards, Madhu On Sat, May 5, 2012 at 1:06 AM, frame wrote: > I am playing sparse checkout feature of subversion. It is working great. > It let me completely ignore the portion of the tree that unrelates to me. > > I just have one thing unclear: > 1)svn checkout https:///proj --depth empty > In my local area, I will have a directory created with name "proj", since > I didn't specify the destination name. The directory is completely empty. > > 2)cd into the proj directory, now is my confusion. I want the whole tree > of proj in my local area. I tried this: > > svn update --depth infinity > //it does not bring anything into my local area > > svn update --set-depth infinity > //yes, it worked > > Reading "svn help update", I cannot figure out the difference. > > Thank you very much. > -- *Thanks, Madhusudhanan*
svn commands and dos redirection
Hi, Under Windows XP, with svn 1.6.17 (I also tried with 1.7.4) running svn pl -R -v . works as expected (I get a line "properties on , followed by the properties), for each item. But when I redirect the same command to a file: svn pl -R . >foo.txt the output in the resulting file is out of order: the "propeties on '.' " line shows up after 658 lines of properties! And it is followed by 100 lines "properties on". There are long blocks of properties without "properties on" header. adding the --xml option keeps the proper order, both on console and when redirected. This makes it difficult to write DOS scripts that handle svn output...I have also tried using loops instead of redirection, but things still show out of order: FOR /F "usebackq tokens=* " %% IN in (`svn pl -R -v .>`) DO (ECHO %%G) I also try piping, no luck, the following gives a messed up output too: svn pl -R -v . | more I ended up looping on each item, calling svn pl each time, but this is painful (dealing with hidden items etc...) svn pg seems to be working. Is it just me? Or a defect? Any workaround (other than --xml or using something more evolved than batch file)? Would there be other commands affected? Thanks Christophe
