From: Florian Weimer <fw@deneb.enyo.de>
To: git@vger.kernel.org
Subject: Re: Does recent 'smart' HTTP feature help git-svn thru unfriendly corp. firewalls too?
Date: Thu, 06 May 2010 14:04:35 +0200 [thread overview]
Message-ID: <87sk6544oc.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <t2td43c95441005050710rb5123219v9ca23aebc01e40ad@mail.gmail.com> (Michael Norman's message of "Wed, 5 May 2010 10:10:20 -0400")
* Michael Norman:
> Subject line says it all - does it help?
The Subversion folks work on a different HTTP-based protocol, which is
supposed to be more proxy/cache-friendly (it's no longer WebDAV).
Until that is deployed on servers, there is little Git can do to
improve the situation.
prev parent reply other threads:[~2010-05-06 12:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-05 14:10 Does recent 'smart' HTTP feature help git-svn thru unfriendly corp. firewalls too? Michael Norman
2010-05-05 14:16 ` Shawn O. Pearce
2010-05-05 14:20 ` Michael Norman
2010-05-05 14:32 ` Scott Chacon
2010-05-05 14:55 ` SVN support at GitHub (was Re: Does recent 'smart' HTTP feature help git-svn thru unfriendly corp. firewalls too?) Matthieu Moy
2010-05-05 15:08 ` Scott Chacon
2010-05-05 14:33 ` Does recent 'smart' HTTP feature help git-svn thru unfriendly corp. firewalls too? Nicolas Pitre
2010-05-06 12:04 ` Florian Weimer [this message]
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=87sk6544oc.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=git@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).