From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] gitweb: Make search type a popup menu
Date: Wed, 11 Oct 2006 23:15:12 +0200 [thread overview]
Message-ID: <egjmt3$bpn$1@sea.gmane.org> (raw)
In-Reply-To: 20061011205817.1855.31725.stgit@rover
Petr Baudis wrote:
> This makes the multiple search types actually usable by the user;
> if you don't read the gitweb source, you don't even have an idea
> that you can write things like that there.
It is on one hand a good idea, for users who doesn't read gitweb
sources. It is like "advanced search" in web search engines.
On the other hand it confirms the notion that search types are exclusive.
Currently pickaxe search is exclusive with log message search, but it is
not necessary. Search operators (now limited) and combining them gives
great search power... or rather would give.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-10-11 21:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-11 20:58 [PATCH] gitweb: Make search type a popup menu Petr Baudis
2006-10-11 21:15 ` Jakub Narebski [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-10-24 3:15 Petr Baudis
2006-10-24 7:33 ` Jakub Narebski
2006-10-24 11:27 ` Petr Baudis
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='egjmt3$bpn$1@sea.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.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).