From: Martin Waitz <tali@admingilde.org>
To: Junio C Hamano <junkio@cox.net>
Cc: Jakub Narebski <jnareb@gmail.com>, git@vger.kernel.org
Subject: Re: gitweb testing with non-apache web server
Date: Thu, 3 Aug 2006 22:14:34 +0200 [thread overview]
Message-ID: <20060803201434.GB5476@admingilde.org> (raw)
In-Reply-To: <7virl9ppy7.fsf@assigned-by-dhcp.cox.net>
[-- Attachment #1: Type: text/plain, Size: 1200 bytes --]
hoi :)
On Thu, Aug 03, 2006 at 12:41:20PM -0700, Junio C Hamano wrote:
> http://www.kernel.org/git/?p=gitk/gitk.git;a=summary
>
> (that's two insertions of 'k').
>
> Now with PATH_INFO, how exactly is this easier?
well, editing is not easier, but you can do other nice things.
On git.admingilde.org I have set up apache to serve the contents
of my git repositories for all the well-known git repository
URLs (*.git/objects/*, *.git/refs/*, ...) and to call gitweb for
all other URLs.
That way I get the exact same URLs for both gitweb and http:// clone
(and even for git://, just change the protocol name).
I really think that it is very handy that you can give out a
repository URL and any user can just click on it and get the
summary page of this project.
I'm sure that it is possible to transfer the PATH_INFO into a p=
parameter through URL rewrite rules, but it is much easier
to set up if gitweb can directly grok appended paths.
I even changed the old gitweb to hand out links which used PATH_INFO
rather than the p= parameter so that the URLs looked nicer.
If there is interest in such a feature then I can do these changes
again.
--
Martin Waitz
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-08-03 20:14 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-03 7:54 gitweb testing with non-apache web server Marc Singer
2006-08-03 8:18 ` Jakub Narebski
2006-08-03 15:34 ` Marc Singer
2006-08-03 15:48 ` Jakub Narebski
2006-08-03 16:20 ` Marc Singer
2006-08-03 18:21 ` Junio C Hamano
2006-08-03 18:37 ` Jakub Narebski
2006-08-03 19:41 ` Junio C Hamano
2006-08-03 20:14 ` Martin Waitz [this message]
2006-08-03 11:42 ` Sam Vilain
2006-08-03 15:56 ` Blu Corater
2006-08-03 16:22 ` Marc Singer
2006-08-03 19:21 ` Blu Corater
2006-08-03 20:27 ` Marc Singer
2006-08-03 23:55 ` Francis Daly
2006-08-04 6:11 ` Marc Singer
2006-08-04 19:48 ` Francis Daly
2006-08-04 7:30 ` Marc Singer
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=20060803201434.GB5476@admingilde.org \
--to=tali@admingilde.org \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=junkio@cox.net \
/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).