From: "Shawn O. Pearce" <spearce@spearce.org>
To: Michael Norman <mwnorman@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Does recent 'smart' HTTP feature help git-svn thru unfriendly corp. firewalls too?
Date: Wed, 5 May 2010 07:16:36 -0700 [thread overview]
Message-ID: <20100505141636.GG11053@spearce.org> (raw)
In-Reply-To: <t2td43c95441005050710rb5123219v9ca23aebc01e40ad@mail.gmail.com>
Michael Norman <mwnorman@gmail.com> wrote:
> Subject line says it all - does it help?
Not sure I can see how/why. The smart HTTP code helps git go
through a firewall, not SVN. SVN already speaks HTTP, just
somewhat inefficiently.
--
Shawn.
next prev parent reply other threads:[~2010-05-05 14:16 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 [this message]
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
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=20100505141636.GG11053@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=mwnorman@gmail.com \
/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.