>
> 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>
> ---
> changes relative to v2[1]:
> - better newline placement in the produced HTML.
>
> Erick Mattos wrote:
>
> > What's up to:
> >
> >
http://thread.gmane.org/gmane.comp.version-control.git/151402/focus=151414
>
> Hopefully third time’s the charm. Test reports welcome as always.