From: Erick Mattos <erick.mattos@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: git@vger.kernel.org, Jakub Narebski <jnareb@gmail.com>,
Pavan Kumar Sunkara <pavan.sss1991@gmail.com>,
Petr Baudis <pasky@suse.cz>,
"John 'Warthog9' Hawley" <warthog9@kernel.org>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: Lost in Space
Date: Tue, 17 Aug 2010 19:42:06 -0300 [thread overview]
Message-ID: <AANLkTimqfCAy6N2w_DPvu5KBe6_8L2zrS91R43LP53J4@mail.gmail.com> (raw)
In-Reply-To: <AANLkTikiVQCMKjftWfrKbK-K+Gv45CTunxjULGc1==Zb@mail.gmail.com>
Hi,
2010/8/7 Jonathan Nieder <jrnieder@gmail.com>
>
> 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.
Nice to see this one in not ignored anymore!
But what about http://thread.gmane.org/gmane.comp.version-control.git/151440/
?!?
I am personally not bothered by being ignored but ignoring the fact
that without this little patch there is a test which is testing
nothing and a necessary check which is not being tested is certainly
not good at all.
Two lines can not be so hard to be accepted without a huge hammer and
so much unpleasant yelling!
Please let's close this issue.
Regards to all
prev parent reply other threads:[~2010-08-17 22:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-07 21:47 Lost in Space Erick Mattos
2010-08-07 21:56 ` [PATCH v3] gitweb: clarify search results page when no matching commit found Jonathan Nieder
2010-08-17 22:42 ` Erick Mattos [this message]
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=AANLkTimqfCAy6N2w_DPvu5KBe6_8L2zrS91R43LP53J4@mail.gmail.com \
--to=erick.mattos@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@gmail.com \
--cc=jrnieder@gmail.com \
--cc=pasky@suse.cz \
--cc=pavan.sss1991@gmail.com \
--cc=warthog9@kernel.org \
/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).