Re: [RFC PATCH 0/8] Git remote helpers to implement smart transports.

From: Shawn O. Pearce <spearce@spearce.org>
Date: Dec 1, 2009, 19:30 UTC
Message-ID: <20091201193009.GM21299@spearce.org>
In-Reply-To: <20091201171908.GA15436@Knoppix>

Ilari Liusvaara <ilari.liusvaara@elisanet.fi> wrote:

Show 10 quoted lines

> On Tue, Dec 01, 2009 at 08:52:45AM -0800, Shawn O. Pearce wrote:
> 
> > Or better, why this is even necessary?
> 
> I have seen requests for gits:// (and in fact, I have plans to
> implement that protocol).
> 
> For instance, to support new types of authentication for smart transports
> without patching client git binaries (SSH has lots of failure modes that
> are quite nasty to debug) or abusing GIT_PROXY (yuck).

So the bulk of this series is about making a proxy for git:// easier to tie into git?

Forgive me if I sound stupid, but for gits:// shouldn't that just be a matter of git_connect() forking a git-remote-gits process linked against openssl? Or, maybe it just runs `openssl s_client`?

Why go through all of this effort of making a really generic proxy
protocol system when the long-term plan is to just ship native
gits:// support as part of git-core?

-- 
Shawn.