From: Mark Lodato <lodatom@gmail.com>
To: git@vger.kernel.org
Subject: Re: Google Code: Support for Mercurial and Analysis of Git and Mercurial
Date: Wed, 29 Apr 2009 20:00:56 -0400 [thread overview]
Message-ID: <ca433830904291700q608f6192i66a83bca9b88b739@mail.gmail.com> (raw)
In-Reply-To: <20090427211502.GI23604@spearce.org>
On Mon, Apr 27, 2009 at 5:15 PM, Shawn O. Pearce <spearce@spearce.org> wrote:
> IOW, if Git wants to expand into these user communities where the
> individual is stuck behind a corporate proxy that only permits HTTP
> "for security reasons" (but blindly winds up passing through whatever
> it gets), we need to support a more efficient HTTP protocol.
Another advantage of supporting HTTP is allowing HTTPS. SSL can take
advantage of an existing PKI infrastructure, either the Internet's
existing server-side certificate system, or a corporate server- and
possibly client-side PKI infrastructure.
--
Mark
prev parent reply other threads:[~2009-04-30 0:01 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-26 5:03 Google Code: Support for Mercurial and Analysis of Git and Mercurial Christian Couder
2009-04-26 7:12 ` Michael Witten
2009-04-26 8:16 ` Jakub Narebski
2009-04-26 8:23 ` Paolo Ciarrocchi
2009-04-26 10:07 ` Johannes Schindelin
2009-04-26 10:16 ` Jakub Narebski
2009-04-26 10:18 ` Johannes Schindelin
2009-04-26 12:02 ` Alex Blewitt
2009-04-27 20:31 ` Shawn O. Pearce
2009-04-26 10:21 ` Paolo Ciarrocchi
2009-04-26 9:21 ` Matthias Andree
2009-04-26 10:09 ` Jakub Narebski
2009-04-26 11:47 ` Matthias Andree
2009-04-26 19:57 ` Jakub Narebski
2009-04-26 14:54 ` A Large Angry SCM
2009-04-26 16:45 ` Michael Witten
2009-04-26 16:56 ` Johannes Schindelin
2009-04-26 17:33 ` A Large Angry SCM
2009-04-26 17:45 ` Johannes Schindelin
2009-04-26 18:00 ` A Large Angry SCM
2009-04-26 18:59 ` James Cloos
2009-04-26 10:13 ` Johannes Schindelin
2009-04-26 16:47 ` Michael Witten
2009-04-26 22:24 ` Miles Bader
2009-04-27 21:15 ` Shawn O. Pearce
2009-04-30 0:00 ` Mark Lodato [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=ca433830904291700q608f6192i66a83bca9b88b739@mail.gmail.com \
--to=lodatom@gmail.com \
--cc=git@vger.kernel.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.
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).