From: Jakub Narebski <jnareb@gmail.com>
To: Christopher Wilson <cwilson@cdwilson.us>
Cc: "Junio C Hamano" <gitster@pobox.com>,
"Alejandro R. Sedeño" <asedeno@mit.edu>,
git@vger.kernel.org
Subject: Re: [PATCH] Enable highlight executable path as a configuration option
Date: Tue, 21 Sep 2010 21:09:40 +0200 [thread overview]
Message-ID: <201009212109.41676.jnareb@gmail.com> (raw)
In-Reply-To: <4C985DDF.8060807@cdwilson.us>
On Tue, 21 Sep 2010, Christopher Wilson wrote:
> Jakub, thanks for the helpful feedback. I included the updated patch
> (see below) which includes the changes you suggested.
> -- >8 --
> Subject: [PATCH] Enable highlight executable path as a configuration option
>
> Allow build-time/run-time configuration of the highlight executable
> (must be the one from http://www.andre-simon.de due to assumptions
> about parameters and output). Defaults to previous behavior which
> assumes that highlight is available on the server PATH. However, if
> this is not the case, the path to the highlight executable can be
> configured at build time as a configuration variable
>
> HIGHLIGHT_BIN = /path/to/highlight
>
> or at runtime by configuring GITWEB_CONFIG
>
> $highlight_bin = /path/to/highlight
>
> Signed-off-by: Christopher Wilson <cwilson@cdwilson.us>
For what it is worth it:
Acked-by: Jakub Narebski <jnareb@gmail.com>
It would certainly be nice to have tests for $highlight_bin, but even
assuming that HIGHLIGHT prerequisite is met, I don't know how such test
could be written. It is not a show-stopper.
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2010-09-21 19:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4C96938C.5050505@cdwilson.us>
2010-09-20 9:10 ` [PATCH] Enable highlight executable path as a configuration option Jakub Narebski
2010-09-21 7:25 ` Christopher Wilson
2010-09-21 19:09 ` Jakub Narebski [this message]
2010-09-19 22:29 Christopher Wilson
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=201009212109.41676.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=asedeno@mit.edu \
--cc=cwilson@cdwilson.us \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).