From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: gitweb testing with non-apache web server
Date: Thu, 03 Aug 2006 20:37:39 +0200 [thread overview]
Message-ID: <eatfog$8er$1@sea.gmane.org> (raw)
In-Reply-To: 7vfygdr888.fsf@assigned-by-dhcp.cox.net
Junio C Hamano wrote:
> Jakub Narebski <jnareb@gmail.com> writes:
>
>>
>> Strange... PATH_INFO is used _only_ if 'p' parameter is not set. And all
>> links use 'p=$project', not PATH_INFO...
>>
>> Are you sure you did changes mentioned in earlier post?
>
> 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.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-08-03 18:37 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 [this message]
2006-08-03 19:41 ` Junio C Hamano
2006-08-03 20:14 ` Martin Waitz
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='eatfog$8er$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
/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.