From: Frank Lichtenheld <djpig@debian.org>
To: martin f krafft <madduck@madduck.net>, 476076@bugs.debian.org
Cc: git discussion list <git@vger.kernel.org>
Subject: Re: Bug#476076: gitweb fails with pathinfo and project with ++ in the name
Date: Sun, 20 Apr 2008 17:53:18 +0200 [thread overview]
Message-ID: <20080420155318.GV6024@mail-vs.djpig.de> (raw)
In-Reply-To: <20080420144654.GA11479@piper.oerlikon.madduck.net>
On Sun, Apr 20, 2008 at 04:46:54PM +0200, martin f krafft wrote:
> The bug seems to be in CGI.pm, and I now wonder what to do about it.
CGI->path_info in etch's version is broken, you need either use a newer
CGI.pm or $ENV{PATH_INFO} directly.
Gruesse,
--
Frank Lichtenheld <djpig@debian.org>
www: http://www.djpig.de/
next prev parent reply other threads:[~2008-04-20 15:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-20 14:46 gitweb fails with pathinfo and project with ++ in the name martin f krafft
2008-04-20 15:53 ` Frank Lichtenheld [this message]
2008-04-20 21:03 ` Bug#476076: " martin f krafft
2008-04-20 21:03 ` [PATCH] Escape project name in regexp martin f. krafft
2008-04-20 21:23 ` [PATCH] Escape project names before creating pathinfo URLs martin f. krafft
2008-04-22 6:31 ` Junio C Hamano
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=20080420155318.GV6024@mail-vs.djpig.de \
--to=djpig@debian.org \
--cc=476076@bugs.debian.org \
--cc=git@vger.kernel.org \
--cc=madduck@madduck.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).