From: Junio C Hamano <junkio@cox.net>
To: Martin Waitz <tali@admingilde.org>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] gitweb: fill in gitweb configuration by Makefile
Date: Sun, 30 Jul 2006 18:20:26 -0700 [thread overview]
Message-ID: <7vzmeqa7tx.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <20060730223754.GA16364@admingilde.org> (Martin Waitz's message of "Mon, 31 Jul 2006 00:37:54 +0200")
Martin Waitz <tali@admingilde.org> writes:
> diff --git a/gitweb/gitweb.cgi b/gitweb/gitweb.pl
> similarity index 100%
> rename from gitweb/gitweb.cgi
> rename to gitweb/gitweb.pl
> index 243a2921f849568260e848201d238b3b9fe7e1f2..8e05c335f801d4c52a9b348fa56fccfae36ce621 100755
> --- a/gitweb/gitweb.cgi
> +++ b/gitweb/gitweb.pl
> @@ -24,14 +24,14 @@ our $rss_link = "";
>
> # core git executable to use
> # this can just be "git" if your webserver has a sensible PATH
> -our $GIT = "/usr/bin/git";
> +our $GIT = "@@GIT_BINDIR@@/git";
>
> # absolute fs-path which will be prepended to the project path
> #our $projectroot = "/pub/scm";
> -our $projectroot = "/home/kay/public_html/pub/scm";
> +our $projectroot = "@@GITWEB_PROJECTROOT@@";
>
> # version of the core git binary
> -our $git_version = qx($GIT --version) =~ m/git version (.*)$/ ? $1 : "unknown";
> +our $git_version = "@@GIT_VERSION@@";
I think the other parts are sensible but I am not sure if we
want to report the version of git distribution (your patch), or
the version of git binary the cgi script happens to use (the
current implementation).
next prev parent reply other threads:[~2006-07-31 1:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-30 22:37 [PATCH] gitweb: fill in gitweb configuration by Makefile Martin Waitz
2006-07-31 1:20 ` Junio C Hamano [this message]
2006-07-31 7:08 ` Martin Waitz
2006-07-31 7:38 ` Jakub Narebski
2006-08-01 19:34 ` Martin Waitz
2006-07-31 8:14 ` Luben Tuikov
2006-07-31 3:57 ` Luben Tuikov
2006-07-31 6:41 ` Junio C Hamano
2006-07-31 7:22 ` Martin Waitz
2006-07-31 9:38 ` Johannes Schindelin
2006-07-31 16:59 ` Luben Tuikov
2006-07-31 21:33 ` Jon Loeliger
2006-07-31 6: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=7vzmeqa7tx.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--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).