From: Michael J Gruber <git@drmicha.warpmail.net>
To: Tay Ray Chuan <rctay89@gmail.com>
Cc: Ilari Liusvaara <ilari.liusvaara@elisanet.fi>,
git@vger.kernel.org, Sverre Rabbelier <srabbelier@gmail.com>,
Avery Pennarun <apenwarr@gmail.com>
Subject: Re: [PATCH 0/3] git over TLS (gits://) support
Date: Mon, 03 May 2010 15:26:23 +0200 [thread overview]
Message-ID: <4BDECEFF.7060900@drmicha.warpmail.net> (raw)
In-Reply-To: <j2tbe6fef0d1005030557l1f746349zfce18213add19efe@mail.gmail.com>
Tay Ray Chuan venit, vidit, dixit 03.05.2010 14:57:
> Hi,
>
> On Sun, May 2, 2010 at 1:09 AM, Ilari Liusvaara
> <ilari.liusvaara@elisanet.fi> wrote:
>> This is newer version of gits:// client side support.
>
> in case anyone is wondering where the older version is, Ilari posted
> it early this year:
>
> http://thread.gmane.org/gmane.comp.version-control.git/136816
>
> From the discussion, Avery (Cc'ed) had some strong objections; the
> point that I remembered the most clearly was "why not just use SSH".
> There didn't seem to be any headway.
>
> I hope that we can continue where we left off and resolve the various
> objections without too much duplication of shot-down arguments.
>
Except for "This is a newer patch" and the split in 3 rather than 2,
there is no information whatsoever on what's different and which
questions have been addressed. Given that, it would be only fair to
raise the same objections again.
Condensing the old thread to a bare minimum, these questions seem to be
open (though answered, one might say):
- What ssh+git: problems does gits: address?
- What tells us these are solved by gits:?
- What tells us there are no gits: problems which ssh+git: would solve?
Frankly, so far I see no tests, no benchmarks, one author convinced by
his own code, and seemingly nobody willing to really look a the patches.
Michael
next prev parent reply other threads:[~2010-05-03 13:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-01 17:09 [PATCH 0/3] git over TLS (gits://) support Ilari Liusvaara
2010-05-01 17:09 ` [PATCH 1/3] git over TLS (gits://) support (part 1) Ilari Liusvaara
2010-05-01 17:09 ` [PATCH 2/3] git over TLS (gits://) support (part 2) Ilari Liusvaara
2010-05-03 9:44 ` Andreas Ericsson
2010-05-01 17:09 ` [PATCH 3/3] git over TLS (gits://) support (part 3) Ilari Liusvaara
2010-05-01 17:17 ` [PATCH 0/3] git over TLS (gits://) support Sverre Rabbelier
2010-05-03 12:57 ` Tay Ray Chuan
2010-05-03 13:26 ` Michael J Gruber [this message]
2010-05-03 17:58 ` Avery Pennarun
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=4BDECEFF.7060900@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=ilari.liusvaara@elisanet.fi \
--cc=rctay89@gmail.com \
--cc=srabbelier@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 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).