From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Cc: John 'Warthog9' Hawley <warthog9@kernel.org>,
admin@repo.or.cz, Jakub Narebski <jnareb@gmail.com>
Subject: [PATCH 0/5] gitweb: Improve search code
Date: Wed, 22 Jun 2011 17:28:50 +0200 [thread overview]
Message-ID: <1308756535-29701-1-git-send-email-jnareb@gmail.com> (raw)
Originally I have intended to go with it further, and improve how
search results look like, for example by using 'log' view code to
display 'commit', 'author' and 'committer' search results, now managed
by git_search_message.
But then I realized that I would need committags machinery for that.
So what we are left with are some code refactoring and cleanups.
Not for 1.7.6 (not a regression fix).
Jakub Narebski (5):
gitweb: 'pickaxe' and 'grep' features requires 'search' to be enabled
gitweb: Check permissions first in git_search
gitweb: Split body of git_search into subroutines
gitweb: Clean up code in git_search_* subroutines
gitweb: Make git_search_* subroutines render whole pages
gitweb/gitweb.perl | 442 ++++++++++++++++++++++++++++-----------------------
1 files changed, 243 insertions(+), 199 deletions(-)
P.S. Another addition that I sometimes wanted git to have would be
'filename' or 'find' search: searching for file by name.
What do you think of it?
--
1.7.5
next reply other threads:[~2011-06-22 15:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-22 15:28 Jakub Narebski [this message]
2011-06-22 15:28 ` [PATCHv3 1/5] gitweb: 'pickaxe' and 'grep' features requires 'search' to be enabled Jakub Narebski
2011-06-22 15:28 ` [PATCH 2/5] gitweb: Check permissions first in git_search Jakub Narebski
2011-06-22 15:28 ` [PATCH 3/5] gitweb: Split body of git_search into subroutines Jakub Narebski
2011-06-22 15:28 ` [PATCH 4/5] gitweb: Clean up code in git_search_* subroutines Jakub Narebski
2011-06-22 15:28 ` [PATCH 5/5] gitweb: Make git_search_* subroutines render whole pages Jakub Narebski
2011-06-22 17:10 ` [PATCH 0/5] gitweb: Improve search code Phil Hord
2011-06-22 18:00 ` Jakub Narebski
2011-06-22 19:24 ` Phil Hord
2011-06-22 18:55 ` Junio C Hamano
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=1308756535-29701-1-git-send-email-jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=admin@repo.or.cz \
--cc=git@vger.kernel.org \
--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).