From: Jakub Narebski <jnareb@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Ramsay Jones <ramsay@ramsay1.demon.co.uk>, git@vger.kernel.org
Subject: Re: [PATCH (BUGFIX)] gitweb: Fix fixed string (non-regexp) project search
Date: Mon, 5 Mar 2012 10:03:10 +0100 [thread overview]
Message-ID: <201203051003.10605.jnareb@gmail.com> (raw)
In-Reply-To: <7vaa3w55i3.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
> Jakub Narebski <jnareb@gmail.com> writes:
>
> > .... The fix is about adding new code and should
> > apply cleanly to 'maint' and even to older versions; the only trouble
> > with older version might be whitespace issue related to refactoring
> > code into subroutines.
>
> OK, so the global $searchtext is what came from form submit from the end
> user, while the global $search_regexp is what the code should be using
> for matching throughout the program, prepared by eval-and-validate-params.
>
> Here is a hand-ported version of your patch that should apply to 1.7.6.6;
> does it look sane?
>
> gitweb/gitweb.perl | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/gitweb/gitweb.perl b/gitweb/gitweb.perl
> index 50a835a..d1698b7 100755
> --- a/gitweb/gitweb.perl
> +++ b/gitweb/gitweb.perl
> @@ -2905,10 +2905,10 @@ sub filter_forks_from_projects_list {
> sub search_projects_list {
> my ($projlist, %opts) = @_;
> my $tagfilter = $opts{'tagfilter'};
> - my $searchtext = $opts{'searchtext'};
> + my $search_re = $opts{'search_regexp'};
>
> return @$projlist
> - unless ($tagfilter || $searchtext);
> + unless ($tagfilter || $search_re);
>
> my @projects;
> PROJECT:
> @@ -2920,10 +2920,10 @@ sub search_projects_list {
> grep { lc($_) eq lc($tagfilter) } keys %{$pr->{'ctags'}};
> }
>
> - if ($searchtext) {
> + if ($search_re) {
> next unless
> - $pr->{'path'} =~ /$searchtext/ ||
> - $pr->{'descr_long'} =~ /$searchtext/;
> + $pr->{'path'} =~ /$search_re/ ||
> + $pr->{'descr_long'} =~ /$search_re/;
> }
>
> push @projects, $pr;
> @@ -5097,7 +5097,7 @@ sub git_project_list_body {
> @projects = fill_project_list_info(\@projects);
> # searching projects require filling to be run before it
> @projects = search_projects_list(\@projects,
> - 'searchtext' => $searchtext,
> + 'search_regexp' => $search_regexp,
> 'tagfilter' => $tagfilter)
> if ($tagfilter || $searchtext);
>
It looks sane, though
@projects = search_projects_list(\@projects,
- 'searchtext' => $searchtext,
+ 'search_regexp' => $search_regexp,
'tagfilter' => $tagfilter)
if ($tagfilter || $searchtext);
should be better written as
@projects = search_projects_list(\@projects,
- 'searchtext' => $searchtext,
+ 'search_regexp' => $search_regexp,
'tagfilter' => $tagfilter)
- if ($tagfilter || $searchtext);
+ if ($tagfilter || $search_regexp);
It is functionally the same, because $search_regexp is derived from
$searchtext, but IMHO it is more clear.
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2012-03-05 9:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-28 18:41 [PATCH (BUGFIX)] gitweb: Handle invalid regexp in regexp search Jakub Narebski
2012-02-28 19:45 ` Junio C Hamano
2012-02-29 15:56 ` Jakub Narebski
2012-03-02 19:44 ` Ramsay Jones
2012-03-02 22:34 ` [PATCH (BUGFIX)] gitweb: Fix fixed string (non-regexp) project search Jakub Narebski
2012-03-03 0:08 ` Junio C Hamano
2012-03-03 10:55 ` Jakub Narebski
2012-03-04 9:35 ` [PATCH (for maint)] " Jakub Narebski
2012-03-05 5:16 ` Junio C Hamano
2012-03-05 8:59 ` Jakub Narebski
2012-03-05 17:01 ` Junio C Hamano
2012-03-05 23:27 ` Junio C Hamano
2012-03-06 11:59 ` Jakub Narebski
2012-03-04 18:00 ` [PATCH (BUGFIX)] " Jakub Narebski
2012-03-04 23:08 ` Junio C Hamano
2012-03-05 9:03 ` Jakub Narebski [this message]
2012-03-05 19:06 ` Ramsay Jones
2012-03-06 12:40 ` 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=201203051003.10605.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=ramsay@ramsay1.demon.co.uk \
/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).