From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Detlef Vollmann <dv@vollmann.ch>,
Jello huang <ruifeihuang@gmail.com>,
git@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: cannot fetch arm git tree
Date: Fri, 21 Jan 2011 16:25:44 +0100 [thread overview]
Message-ID: <20110121152544.GQ14956@pengutronix.de> (raw)
In-Reply-To: <20110121145025.GS13235@n2100.arm.linux.org.uk>
On Fri, Jan 21, 2011 at 02:50:26PM +0000, Russell King - ARM Linux wrote:
> On Fri, Jan 21, 2011 at 03:28:14PM +0100, Detlef Vollmann wrote:
> > It seems to be an implementation of the git protocol using
> > HTTP as transport.
> > Some info on this is at <http://progit.org/2010/03/04/smart-http.html>.
>
> Setting up Smart HTTP
>
> ...
> To set it up, it■s best to walk through the instructions on the
> `git-http-backend` documentation page. Basically, you have to install Git
> v1.6.6 or higher on a server with an Apache 2.x webserver (it has to be
> Apache, currently - other CGI servers don■t work, last I checked). Then
> you add something similar to this to your http.conf file:
>
> SetEnv GIT_PROJECT_ROOT /var/www/git
> SetEnv GIT_HTTP_EXPORT_ALL
> ScriptAlias /git/ /usr/libexec/git-core/git-http-backend/
>
> Great. Deciding that it will be http://servername.example.com/git/ is
> really damned annoying as that's traditionally where gitweb lives,
> which requires a different script alias.
>
> It seems that due to a lack of coordination between different git
> developers, people running webservers have a choice between providing
> gitweb or this http extension.
>
> I'm really not interested in working out how to bodge this into working
> along side the existing gitweb setup by adding lots of rewrite rules, so
> as gitweb got there first I think it has priority, that's what we have
> and we'll have to live without the smart http extensions.
IIRC it's designed to live along side the http:// clone url.
git-http-backend can still serve dumb http clients including a web
browser.
But note that as git-http-backend less info it has to calculate much
more. So the load it introduces should be comparable to running
git-daemon as should be the times to fetch from it. So AFAIK the only
reason to run it is that more corporate users can access port 80.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next prev parent reply other threads:[~2011-01-21 15:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTikRrewCLGDTU7DjVssjpxz-EFK8AhRScAGPRumg@mail.gmail.com>
[not found] ` <20110116092315.GA27542@n2100.arm.linux.org.uk>
2011-01-16 11:08 ` cannot fetch arm git tree Uwe Kleine-König
[not found] ` <AANLkTinrZ0GnT71GCueUUpAXM5ckq+LBd0RjA51DMR-a@mail.gmail.com>
2011-01-16 13:42 ` Russell King - ARM Linux
2011-01-17 1:49 ` Jello huang
2011-01-21 13:38 ` Detlef Vollmann
2011-01-21 13:47 ` Uwe Kleine-König
2011-01-21 13:57 ` Russell King - ARM Linux
2011-01-21 14:28 ` Detlef Vollmann
2011-01-21 14:30 ` Jello huang
2011-01-21 14:50 ` Russell King - ARM Linux
2011-01-21 15:14 ` Detlef Vollmann
2011-01-21 15:25 ` Uwe Kleine-König [this message]
2011-01-24 5:01 ` Miles Bader
2011-01-24 7:21 ` Johannes Sixt
2011-01-24 7:34 ` J.H.
2011-01-24 10:53 ` Russell King - ARM Linux
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=20110121152544.GQ14956@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--cc=dv@vollmann.ch \
--cc=git@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux@arm.linux.org.uk \
--cc=ruifeihuang@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.
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).