All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Detlef Vollmann <dv@vollmann.ch>
Cc: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"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 14:50:26 +0000	[thread overview]
Message-ID: <20110121145025.GS13235@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <4D3997FE.5030109@vollmann.ch>

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.

It's really not that big a deal if you follow the advice I've given.

WARNING: multiple messages have this Message-ID (diff)
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: cannot fetch arm git tree
Date: Fri, 21 Jan 2011 14:50:26 +0000	[thread overview]
Message-ID: <20110121145025.GS13235@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <4D3997FE.5030109@vollmann.ch>

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.

It's really not that big a deal if you follow the advice I've given.

  parent reply	other threads:[~2011-01-21 14:51 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-16  2:28 cannot fetch arm git tree Jello huang
2011-01-16  9:23 ` Russell King - ARM Linux
2011-01-16 11:08   ` Uwe Kleine-König
2011-01-16 11:08     ` Uwe Kleine-König
     [not found]     ` <AANLkTinrZ0GnT71GCueUUpAXM5ckq+LBd0RjA51DMR-a@mail.gmail.com>
2011-01-16 13:42       ` Russell King - ARM Linux
2011-01-16 13:42         ` Russell King - ARM Linux
2011-01-17  1:49         ` Jello huang
2011-01-17  1:49           ` Jello huang
2011-01-21 13:38         ` Detlef Vollmann
2011-01-21 13:38           ` Detlef Vollmann
2011-01-21 13:47           ` Uwe Kleine-König
2011-01-21 13:47             ` Uwe Kleine-König
2011-01-21 13:57             ` Russell King - ARM Linux
2011-01-21 13:57               ` Russell King - ARM Linux
2011-01-21 14:28               ` Detlef Vollmann
2011-01-21 14:28                 ` Detlef Vollmann
2011-01-21 14:30                 ` Jello huang
2011-01-21 14:30                   ` Jello huang
2011-01-21 14:50                 ` Russell King - ARM Linux [this message]
2011-01-21 14:50                   ` Russell King - ARM Linux
2011-01-21 15:14                   ` Detlef Vollmann
2011-01-21 15:14                     ` Detlef Vollmann
2011-01-21 15:25                   ` Uwe Kleine-König
2011-01-21 15:25                     ` Uwe Kleine-König
2011-01-24  5:01                   ` Miles Bader
2011-01-24  5:01                     ` Miles Bader
2011-01-24  7:21                   ` Johannes Sixt
2011-01-24  7:21                     ` Johannes Sixt
2011-01-24  7:34                     ` J.H.
2011-01-24  7:34                       ` J.H.
2011-01-24 10:53                     ` Russell King - ARM Linux
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110121145025.GS13235@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=dv@vollmann.ch \
    --cc=git@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=ruifeihuang@gmail.com \
    --cc=u.kleine-koenig@pengutronix.de \
    /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.