From: Jakub Narebski <jnareb@gmail.com>
To: Marc Branchaud <marcnarc@xiplink.com>
Cc: git@vger.kernel.org, Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Subject: Re: [RFC/PATCH] Changed gitweb.remote_heads config key name to gitweb.remoteHeads.
Date: Thu, 7 Jul 2011 22:36:50 +0200 [thread overview]
Message-ID: <201107072236.51183.jnareb@gmail.com> (raw)
In-Reply-To: <201107072056.25417.jnareb@gmail.com>
> -- >8 --
> From: Jakub Narebski <jnareb@gmail.com>
> Date: Thu, 7 Jul 2011 20:48:50 +0200
> Subject: [PATCH] gitweb: Make git config search case insensitive
I should have probably add here the following:
The section and key part of fully qualified name of config variable
are case insensitive in git. "git config --list -z" that gitweb uses
returns them lowercased.
> Gitweb does not (yet?) use git config variables with subsection, so we
> can simply lowercase $key in git_get_project_config: section name and
> key name are case insensitive (only subsection name is case
> sensitive).
>
> Signed-off-by: Jakub Narebski <jnareb@gmail.com>
> ---
Yet another case where commit message is longer than fix... ;-)
> gitweb/gitweb.perl | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/gitweb/gitweb.perl b/gitweb/gitweb.perl
> index 589c85b..59147b6 100755
> --- a/gitweb/gitweb.perl
> +++ b/gitweb/gitweb.perl
> @@ -2526,6 +2526,7 @@ sub git_get_project_config {
>
> # key sanity check
> return unless ($key);
> + $key = lc($key); # assuming there is no subsection
> $key =~ s/^gitweb\.//;
> return if ($key =~ m/\W/);
>
> --
> 1.7.5
>
>
--
Jakub Narebski
Poland
prev parent reply other threads:[~2011-07-07 20:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-07 18:02 [RFC/PATCH] Changed gitweb.remote_heads config key name to gitweb.remoteHeads Marc Branchaud
2011-07-07 18:56 ` Jakub Narebski
2011-07-07 20:36 ` Jakub Narebski [this message]
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=201107072236.51183.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=giuseppe.bilotta@gmail.com \
--cc=marcnarc@xiplink.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).