From: Jeff King <peff@peff.net>
To: Sergey Sharybin <sergey.vfx@gmail.com>
Cc: Konstantin Khomoutov <flatworm@users.sourceforge.net>,
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
Andreas Schwab <schwab@linux-m68k.org>,
Git List <git@vger.kernel.org>
Subject: Re: git:// protocol over SSL/TLS
Date: Sat, 28 Dec 2013 04:37:51 -0500 [thread overview]
Message-ID: <20131228093751.GD21109@sigill.intra.peff.net> (raw)
In-Reply-To: <CAErtv25uWbsH15yohh+6Jun3eD51dZzvj7udoBf14_EwXzSUPg@mail.gmail.com>
On Fri, Dec 27, 2013 at 08:47:54PM +0600, Sergey Sharybin wrote:
> > The web server software has nothing to do with HTTP[S] used by Git being
> > "smart", I think, it just has to be set up properly.
>
> Misunderstood git doc then which says "it has to be Apache, currently
> - other CGI servers don't work, last I checked".
Do you happen to remember where you saw that claim? If the manual in
git's Documentation/ directory says that, I'd like to fix it.
I added sample lighttpd config to "git help http-backend" a while back.
I tested it at the time, but I do not currently run a lighttpd git
server at all.
-Peff
next prev parent reply other threads:[~2013-12-28 9:37 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-27 12:59 git:// protocol over SSL/TLS Sergey Sharybin
2013-12-27 13:29 ` Andreas Schwab
2013-12-27 13:36 ` Konstantin Khomoutov
2013-12-27 13:58 ` Sergey Sharybin
2013-12-27 14:12 ` Andreas Schwab
2013-12-27 14:16 ` Konstantin Khomoutov
2013-12-27 14:18 ` Sergey Sharybin
2013-12-27 14:20 ` Matthieu Moy
2013-12-27 14:25 ` Sergey Sharybin
2013-12-27 14:39 ` Konstantin Khomoutov
2013-12-27 14:47 ` Sergey Sharybin
2013-12-27 14:56 ` Konstantin Khomoutov
2013-12-28 9:37 ` Jeff King [this message]
2013-12-27 16:26 ` Bernhard R. Link
2013-12-28 20:52 ` Sergey Sharybin
2013-12-28 0:11 ` brian m. carlson
2013-12-27 14:29 ` Andreas Schwab
2013-12-27 14:21 ` Pyeron, Jason J CTR (US)
2013-12-27 14:14 ` Konstantin Khomoutov
2013-12-27 22:21 ` Junio C Hamano
2013-12-28 20:00 ` Ilari Liusvaara
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=20131228093751.GD21109@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=flatworm@users.sourceforge.net \
--cc=git@vger.kernel.org \
--cc=schwab@linux-m68k.org \
--cc=sergey.vfx@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.