git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Avery Pennarun <apenwarr@gmail.com>
To: Tay Ray Chuan <rctay89@gmail.com>
Cc: Ilari Liusvaara <ilari.liusvaara@elisanet.fi>,
	git@vger.kernel.org, Sverre Rabbelier <srabbelier@gmail.com>
Subject: Re: [PATCH 0/3] git over TLS (gits://) support
Date: Mon, 3 May 2010 13:58:05 -0400	[thread overview]
Message-ID: <s2h32541b131005031058o4d2df47ei7fcd5205db89eeb7@mail.gmail.com> (raw)
In-Reply-To: <j2tbe6fef0d1005030557l1f746349zfce18213add19efe@mail.gmail.com>

On Mon, May 3, 2010 at 8:57 AM, Tay Ray Chuan <rctay89@gmail.com> wrote:
> 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.

After more consideration, I withdraw my objection since the fact that
I don't need it, nor does anybody I know need it, isn't actually a
good argument against including it.  I assume the Powers That Be would
still like to see some people who *do* need it before including such a
huge chunk of code.

Have fun,

Avery

      parent reply	other threads:[~2010-05-03 17:58 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
2010-05-03 17:58   ` Avery Pennarun [this message]

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=s2h32541b131005031058o4d2df47ei7fcd5205db89eeb7@mail.gmail.com \
    --to=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).