From: Jakub Narebski <jnareb@gmail.com>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [RFC/PATCH (take 3)] gitweb: Add some mod_perl specific support
Date: Sat, 16 Dec 2006 21:03:17 +0100 [thread overview]
Message-ID: <200612162103.18695.jnareb@gmail.com> (raw)
In-Reply-To: <7virgbei6z.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> I have your (take 2) merged already last night in my tree but
> haven't pushed the result out. Does this replace it?
Yes, that replaces it. I'm very sorry for the confusion.
I have noticed that I would need to add "use Apache2::RequestRec"
or it's mod_perl 1.0 equivalent before I can use $r->path_info().
--
Jakub Narebski
next prev parent reply other threads:[~2006-12-16 20:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-15 21:18 [PATCH] gitweb: Add some mod_perl specific support Jakub Narebski
2006-12-16 16:12 ` [RFC/PATCH (take 3)] " Jakub Narebski
2006-12-16 19:47 ` Junio C Hamano
2006-12-16 20:03 ` Jakub Narebski [this message]
2006-12-16 21:30 ` 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=200612162103.18695.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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).