diff options
author | Jonathan Nieder <jrnieder@gmail.com> | 2010-08-07 16:56:47 -0500 |
---|---|---|
committer | Junio C Hamano <gitster@pobox.com> | 2010-08-09 13:05:35 -0700 |
commit | 497d9c343902591e98a6612385d529816420ea94 (patch) | |
tree | 58d5bfc0dd6b6a654986bc266c89625f9050c144 /pack-refs.h | |
parent | 977ed83a6da635332a0c9e4cdd8b7e1715a9d363 (diff) | |
download | git-497d9c343902591e98a6612385d529816420ea94.tar.gz git-497d9c343902591e98a6612385d529816420ea94.tar.xz |
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>
Diffstat (limited to 'pack-refs.h')
0 files changed, 0 insertions, 0 deletions