git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Petr Baudis <pasky@suse.cz>, git@vger.kernel.org
Subject: Re: [PATCH] gitweb: Even more support for PATH_INFO based URLs
Date: Sat, 23 Sep 2006 16:55:49 +0200	[thread overview]
Message-ID: <200609231655.49915.jnareb@gmail.com> (raw)
In-Reply-To: <20060923142941.GL8259@pasky.or.cz>

Petr Baudis wrote:
> Dear diary, on Wed, Sep 20, 2006 at 12:49:51AM CEST, I got a letter
> where Jakub Narebski <jnareb@gmail.com> said that...
> > Now the following types of path based URLs are supported:
> > 
> > * project              overview (summary) page of project
> > * project/branch       shortlog of branch
> > * project/branch:file  file in branch, blob_plain view
> > * project/branch:dir/  directory listing of dir in branch, tree view
> > 
> > The following shortcuts works (see explanation below):
> > 
> > * project/branch:      directory listing of branch, main tree view
> > * project/:file        file in HEAD (raw)
> > * project/:dir/        directory listing of dir in HEAD
> > * project/:            directory listing of project's HEAD
> 
>   I haven't followed this stuff carefully but just to confirm, there is
> currently no way to persuade gitweb to actually produce such links,
> right?
> 
>   I like pathinfo and would like to use it for repo.or.cz's gitweb.

Well, all inner links go through href() subroutine, so this is where
you would want to make changes. Having project in pathinfo would be easy,
having branch/ref harder because it might be in hash, or in hash_base
parameter.

Perhaps we should use
	my $path_info = $ENV{MOD_PERL} ? $r->path_info() : $ENV{PATH_INFO};
-- 
Jakub Narebski
Poland

      reply	other threads:[~2006-09-23 14:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-19 22:49 [PATCH] gitweb: Even more support for PATH_INFO based URLs Jakub Narebski
2006-09-20 21:04 ` Martin Waitz
2006-09-23 14:29 ` Petr Baudis
2006-09-23 14:55   ` Jakub Narebski [this message]

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=200609231655.49915.jnareb@gmail.com \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=pasky@suse.cz \
    /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).