From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] eglibc: use HTTP for svn checkout
Date: Tue, 14 Dec 2010 09:55:57 -0700 [thread overview]
Message-ID: <4D07A19D.8090602@mentor.com> (raw)
In-Reply-To: <4D079B88.9010503@dell.com>
On 12/14/2010 09:30 AM, Ryan D Phillips wrote:
> On 12/13/2010 2:00 PM, Khem Raj wrote:
>> On Mon, Dec 13, 2010 at 9:13 AM, Ryan D Phillips
>> <ryan_d_phillips@dell.com> wrote:
>>> SVN over HTTP is a more reliable transport for developers behind
>>> restrictive
>>> proxies.
>>>
>>
>> and how much slower/faster is it when compared to svn protocol ?
>>
>
> The speed depends on which subversion client backend someone is using.
> HTTP will be slower than using the svn native protocol, but the serf
> subversion backend will perform parallel fetches.
>
> I would like to see this patch get into the OE tree to make the tree
> more robust to proxies. Currently, this is the only customization I need
> for the projects I work on.
Note that if you use a mirror site with the SVN checkout archive in it,
you won't try and do the fetch at all. This may or may not be
applicable to your case. For your case I think what we really want is a
way to globally toggle the svn protocol argument.
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2010-12-14 16:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-13 17:13 [PATCH] eglibc: use HTTP for svn checkout Ryan D Phillips
2010-12-13 20:00 ` Khem Raj
2010-12-14 16:30 ` Ryan D Phillips
2010-12-14 16:55 ` Tom Rini [this message]
2010-12-14 17:11 ` Khem Raj
2010-12-15 16:35 ` Chris Larson
2010-12-15 16:43 ` Andreas Oberritter
2010-12-15 16:45 ` Chris Larson
2010-12-14 17:09 ` Khem Raj
2010-12-15 10:32 ` Enrico Scholz
2010-12-14 7:57 ` Aeschbacher, Fabrice
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D07A19D.8090602@mentor.com \
--to=tom_rini@mentor.com \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.