From: Junio C Hamano <junkio@cox.net>
Date: Thu, 03 Aug 2006 19:41:20 GMT
Subject: Re: gitweb testing with non-apache web server
Message-ID: <7virl9ppy7.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <eatfog$8er$1@sea.gmane.org>

Jakub Narebski <jnareb@gmail.com> writes:

> Junio C Hamano wrote:
>
>> Well, more importantly, why would we do something like this in the first 
>> place?
>> 
>> Wouldn't it be a lot better to just rip out PATH_INFO stuff,
>> especially since all pages the script generates use ?p=$project 
>> to pass that information around and never uses PATH_INFO?
>
> The PATH_INFO is here because it is easier to edit parameters by hand when
> the most important one, the project to examine, can be passed as PATH_INFO.

Huh?  I do not get that.

Suppose I am looking at my repository.  I visit there from my
Firefox and see this in the location bar:

	http://www.kernel.org/git/?p=git/git.git;a=summary

Now I would want to check if there are updates to gitk.  So I
click on the location bar, and edit it to:

	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?