]> Lady’s Gitweb - Gitweb/commit
gitweb: clarify search results page when no matching commit found
authorJonathan Nieder <redacted>
Sat, 7 Aug 2010 21:56:47 +0000 (16:56 -0500)
committerLady <redacted>
Mon, 6 Apr 2026 04:51:30 +0000 (00:51 -0400)
commite5db19433e39da4191988e5db45f8984f6f00144f3b16109d5536f71da776ef3
treebccc6809ca509a92f7aec1724d67053b24b339745dbeffd8915324d54cbb8f13
parentc96f1eef6df16a5a98c0644bd4f8fb2f735bd9b010f0cafe77af921e2f6efc6a
gitweb: clarify search results page when no matching commit found

When searching commits for a string that never occurs, the results
page looks something like this:

projects / foo.git / search                                 \o/
summary | ... | tree          [commit] search: [ kfjdkas ] [ ]re
first ⋅ prev ⋅ next

Merge branch 'maint'

Foo: a demonstration project

Without a list of hits to compare it to, the header describing the
commit named by the hash parameter (usually HEAD) may itself look
like a hit.  Add some text (“No match.”) to replace the empty
list of hits and avoid this confusion.

While at it, remove some nearby dead code, left behind from a
simplification a few years ago (v1.5.4-rc0~276^2~4, 2007-11-01).

Noticed-by: Erick Mattos <redacted>
Signed-off-by: Jonathan Nieder <redacted>
Acked-by: Jakub Narebski <redacted>
Signed-off-by: Junio C Hamano <redacted>
gitweb.perl
This page took 0.312473 seconds and 4 git commands to generate.