gitweb: clarify search results page when no matching commit found
commit52847bab35cf070fee61a3ded03181277ddbfe61
authorJonathan Nieder <jrnieder@gmail.com>
Sat, 7 Aug 2010 21:56:47 +0000 (7 16:56 -0500)
committerKyle J. McKay <mackyle@gmail.com>
Sun, 2 Feb 2014 10:30:50 +0000 (2 02:30 -0800)
tree6b36bf360b4098449a8706013fc8bd6e8fdce423
parentef3754069445d97194f514612f5c53974009d016
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 <erick.mattos@gmail.com>
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Acked-by: Jakub Narebski <jnareb@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
gitweb/gitweb.perl