Subject line says it all - does it help?
Thanks in advance, --- Mike Norman
threads / discuss / 23708
Does recent 'smart' HTTP feature help git-svn thru unfriendly corp. firewalls too?
Subject: Does recent 'smart' HTTP feature help git-svn thru unfriendly corp. firewalls too?
Shawn O. PearceRe: Does recent 'smart' HTTP feature help git-svn thru unfriendly corp. firewalls too?
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.
Re: Does recent 'smart' HTTP feature help git-svn thru unfriendly corp. firewalls too?
Sigh - most SVN installations require ssh+svn for read/write access.
Our company is changing firewall vendors and I have been told that our TortoisePlink+putty-session 'trick' may be blocked :-(
On Wed, May 5, 2010 at 10:16 AM, Shawn O. Pearce <spearce@spearce.org> wrote:
Show 10 quoted lines
> 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. >
Scott ChaconRe: Does recent 'smart' HTTP feature help git-svn thru unfriendly corp. firewalls too?
Hey,
On Wed, May 5, 2010 at 7:20 AM, Michael Norman <mwnorman@gmail.com> wrote:
> Sigh - most SVN installations require ssh+svn for read/write access. > > Our company is changing firewall vendors and I have been told that our > TortoisePlink+putty-session 'trick' may be blocked :-(
You can use GitHub for native SVN and Git access, both over http - that will allow you to use Git as the main repository as it should be. :)
Scott
Matthieu MoySVN support at GitHub (was Re: Does recent 'smart' HTTP feature help git-svn thru unfriendly corp. firewalls too?)
Scott Chacon <schacon@gmail.com> writes:
> You can use GitHub for native SVN and Git access, both over http - > that will allow you to use Git as the main repository as it should be. > :)
Wow, that's neat!
Is it a private GitHub thing, or some open source code that other people can install on their own server?
-- Matthieu Moy http://www-verimag.imag.fr/~moy/
Scott ChaconRe: SVN support at GitHub (was Re: Does recent 'smart' HTTP feature help git-svn thru unfriendly corp. firewalls too?)
Hey,
On Wed, May 5, 2010 at 7:55 AM, Matthieu Moy <Matthieu.Moy@grenoble-inp.fr> wrote:
Show 11 quoted lines
> Scott Chacon <schacon@gmail.com> writes: > >> You can use GitHub for native SVN and Git access, both over http - >> that will allow you to use Git as the main repository as it should be. >> :) > > Wow, that's neat! > > Is it a private GitHub thing, or some open source code that other > people can install on their own server? >
Right now our version is very tied to our weird infrastructure, and thus would not be generally useful, but I would like to fix and open source it someday. Currently it's not much different than the HeeChee project, however, which does largely the same thing, but for both Hg and Git. If you're interested, I would check that out:
http://bitbucket.org/andrewgodwin/heechee/
Scott
> -- > Matthieu Moy > http://www-verimag.imag.fr/~moy/ >
Nicolas PitreRe: Does recent 'smart' HTTP feature help git-svn thru unfriendly corp. firewalls too?
On Wed, 5 May 2010, Michael Norman wrote:
> Sigh - most SVN installations require ssh+svn for read/write access. > > Our company is changing firewall vendors and I have been told that our > TortoisePlink+putty-session 'trick' may be blocked :-(
Any firewall installation ought to be configurable and allow for letting through selected ssh connections. If no I suggest you change firewall vendors again.
Nicolas
Re: Does recent 'smart' HTTP feature help git-svn thru unfriendly corp. firewalls too?
* 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.