From: Ilari Liusvaara <ilari.liusvaara@elisanet.fi>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>, Jeff King <peff@peff.net>,
spearce@spearce.org,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: Is anyone working on a next-gen Git protocol?
Date: Sun, 7 Oct 2012 23:22:20 +0300 [thread overview]
Message-ID: <20121007202220.GA16115@LK-Perkele-VI.localdomain> (raw)
In-Reply-To: <CACBZZX6b+3P8M+z+X13k9Pq3tvVUfs_k1=foQVreX8K801=efQ@mail.gmail.com>
On Sun, Oct 07, 2012 at 09:57:56PM +0200, Ævar Arnfjörð Bjarmason wrote:
>
> Has anyone started working on a next-gen Git protocol as a result of
> this discussion? If not I thought I'd give it a shot if/when I have
> time.
Unfortunately, client signaling the version is nasty to do in ways that
wouldn't cause current servers to hang up or do other undesirable things.
git://: Git-daemon will hang up[1] if it receives command it won't
understand (and one can't add arguments either).
ssh://: Commands are NAKed in non-standard ways (e.g. Gitolite vs. shell)
and one can't add arguments.
file://: That's easy.
CONNECT: The helper needs to be told that v2 is supported (helper doing
the rest).
Maybe with git://, one could hack the stuff in similar way as virtual
hosting was added. But that won't work with SSH (nor one can use environment
with SSH).
:-/
[1] And there is no guarantee that the server end of git:// is git-daemon.
There's at least one git:// server implemetation that responds to unknown
commands by ERR packet followed by hangup.
-Ilari
next prev parent reply other threads:[~2012-10-07 20:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-07 19:57 Is anyone working on a next-gen Git protocol? Ævar Arnfjörð Bjarmason
2012-10-07 20:22 ` Ilari Liusvaara [this message]
2012-10-07 22:08 ` Jeff King
2012-10-07 22:31 ` Junio C Hamano
2012-10-22 4:59 ` Junio C Hamano
2012-10-08 9:05 ` Andreas Ericsson
2012-10-08 16:27 ` Junio C Hamano
2012-10-10 19:13 ` Steffen Prohaska
2012-10-10 20:46 ` Junio C Hamano
2012-10-10 22:32 ` Philip Oakley
2012-10-11 1:44 ` Nguyen Thai Ngoc Duy
2012-10-11 3:08 ` Shawn Pearce
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121007202220.GA16115@LK-Perkele-VI.localdomain \
--to=ilari.liusvaara@elisanet.fi \
--cc=Johannes.Schindelin@gmx.de \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=spearce@spearce.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).