<br><br><div class="gmail_quote">On Thu, May 6, 2010 at 3:52 PM, Andersen Max <span dir="ltr"><<a href="mailto:max.andersen@redhat.com">max.andersen@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
(redirecting to the right list )<br>
<font color="#888888"><br>
-max<br>
</font><div><div></div><div class="h5"><br>
On May 6, 2010, at 10:13, Andersen Max wrote:<br>
<br>
><br>
> On May 5, 2010, at 10:26, Yahor Radtsevich wrote:<br>
><br>
>> Hi Max,<br>
>><br>
>> Regular svn updates (with short delta) are acceptable fast (5-10min under Windows), but in the cases when an old version is needed or to do svn switch, the updates are much longer:<br>
>> svn update -r21899 (from r21862, 2 days old): 7m9s<br>
>> svn update -r21862 (from r21485, 3 weeks old): 1h12m<br>
>> svn update -r21888 (from r20458, 2.5 months old): 2h57m<br>
>><br>
><br>
> How often do you do such operations ?<br></div></div></blockquote><div>I do them to get fresh updates, to commit to both brunches, and sometimes to find the version in which a bug is introduced. Last month, because of xulrunner and docs in trunk, my updates took ~8 hours.<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div><div class="h5"><br>
> Those times doesn't sound like something excluding documentation will fix, nor<br>
> do they look extremely slow for a large codebase ?<br></div></div></blockquote><div>By deleting all docs from trunk and moving xulrunner to a different directory, the time of 21485 to 21862 updating has reduced to 0h29m (better than 2x improvement).<br>
</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div><div class="h5">
><br>
>> Under Linux short updates take 1-2min, and there is no difference for long ones.<br>
><br>
> So the problem is windows ?<br></div></div></blockquote><div>I mean that long updates take approximately the same time on both systems. Thus no, windows is not the problem.<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<div><div class="h5">
><br>
> /max<br>
>><br>
>><br>
>> On Tue, May 4, 2010 at 1:38 PM, Andersen Max <<a href="mailto:max.andersen@redhat.com">max.andersen@redhat.com</a>> wrote:<br>
>> Thanks for the tip...but How loong are those updates ?<br>
>><br>
>> doing an svn update for me takes less than 1 minute, sometimes 1.5 minute.<br>
>><br>
>> Rob (who is in China) just did it in 90 seconds from a coffee shop.<br>
>><br>
>> What is the time for you ?<br>
>><br>
>> /max<br>
>><br>
>> On May 4, 2010, at 11:01, Yahor Radtsevich wrote:<br>
>><br>
>>> Hi All,<br>
>>><br>
>>> If you, like me, are annoyed by looooong time of trunk updates, there is a SVN feature to skip directories you do not use. This feature is called 'Sparse Directories'.<br>
>>><br>
>>> For example, to delete directory 'documentation' from your local copy of trunk permanently, use the following command:<br>
>>> svn update --set-depth empty documentation<br>
>>> After this command, the documentation directory will be skipped during further updates and switches. (To restore it back, use --set-depth infinity).<br>
>>><br>
>>> Windows users may use the following batch-script to delete all documentation and *\docs directories at once (just save as deletedocs.bat and run from trunk directory):<br>
>>> @echo DELETING OF documentation...<br>
>>> svn update --set-depth empty documentation<br>
>>> @echo DELETING OF *\docs:<br>
>>> @FOR /f %%d IN ('dir /b /a:d') DO (<br>
>>> @IF EXIST %%d\docs\.svn (<br>
>>> @echo DELETING OF %%d\docs...<br>
>>> svn update --set-depth empty %%d\docs<br>
>>> )<br>
>>> )<br>
>>><br>
>>><br>
>>> Best Regards,<br>
>>> Yahor Radtsevich<br>
>>><br>
>>> _______________________________________________<br>
>>> jbosstools-dev mailing list<br>
>>> <a href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</a><br>
>>> <a href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a><br>
>><br>
>><br>
><br>
><br>
<br>
</div></div></blockquote></div><br>