From: Petr Baudis <pasky@suse.cz>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org, Martin Waitz <tali@admingilde.org>,
Matthias Lederhofer <matled@gmx.net>
Subject: Re: [PATCH] gitweb: Even more support for PATH_INFO based URLs
Date: Sat, 23 Sep 2006 16:29:41 +0200 [thread overview]
Message-ID: <20060923142941.GL8259@pasky.or.cz> (raw)
In-Reply-To: <200609200049.52036.jnareb@gmail.com>
Hi,
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.
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
#!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1
lK[d2%Sa2/d0$^Ixp"|dc`;s/\W//g;$_=pack('H*',/((..)*)$/)
next prev parent reply other threads:[~2006-09-23 14:29 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 [this message]
2006-09-23 14:55 ` Jakub Narebski
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=20060923142941.GL8259@pasky.or.cz \
--to=pasky@suse.cz \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=matled@gmx.net \
--cc=tali@admingilde.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 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).