From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Cc: John 'Warthog9' Hawley <warthog9@eaglescrag.net>,
John 'Warthog9' Hawley <warthog9@kernel.org>,
Uwe Kleine-Koenig <u.kleine-koenig@pengutronix.de>,
Jonathan Nieder <jrnieder@gmail.com>, Petr Baudis <pasky@suse.cz>,
Sebastien Cevey <seb@cine7.net>,
Jakub Narebski <jnareb@gmail.com>
Subject: [PATCH 0/6] gitweb: Improve ctags, introduce categories
Date: Fri, 29 Apr 2011 19:51:55 +0200 [thread overview]
Message-ID: <1304099521-27617-1-git-send-email-jnareb@gmail.com> (raw)
This series is composed of two independent parts: improvements to
content tags (ctags) handling in patches 2-3, and introducing optional
grouping of projects by categories in patches 4-6 (where 4-5 are
preparatory).
Both of those series are based on 1st patch in series which
restructures how projects list is being generated, to make those
changes easy to introduce. Because both of those depend on the same
introductory patch they are put in single series... that and the fact
that there was trivial conflict to be resolved in rebasing 'project
category' part on top of 'ctags' part.
Table of contents:
~~~~~~~~~~~~~~~~~~
* [PATCH 1/6 (v2)] gitweb: Restructure projects list generation
This patch extracts filtering out "forks" and searching for projects
(i.e. limiting listed projects) into separate subroutines. Also
filtering is done upfront and not while printing. This makes for
more clear code and makes subsequent changes much easier.
Filtering forks is now faster thanks to using trie; see comments in
code and in the patch itself.
* [PATCH 2/6] gitweb: Change the way "content tags" ('ctags') are handled
Making ctags info parsing more robust sort of fixes bug noticed in
gitweb: cloud tags feature produces malformed XML for errors
http://thread.gmane.org/gmane.linux.debian.devel.bugs.general/802865/focus=168266
http://bugs.debian.org/616005
caused by myshandling underdocumented then 'ctags' feature. This
patch DOES NOT however resolve deeper fundamental problem with error
/ exception handling in gitweb after some data was already sent to a
browser.
It also removes gitweb half of interface for adding content tags
(labels) to a project; it was quarter of feature at best (there
is/was no example implementation of server side half of adding
content tags, no way to delete or fix content tags).
* [PATCH 3/6] gitweb: Mark matched 'ctag' / contents tag (?by_tag=foo)
This is simple improvement, done while working on 'ctags' feature.
* [PATCH 4/6] gitweb: Split git_project_list_body in two functions
[PATCH 5/6] gitweb: Modularized git_get_project_description to be more generic
Those two patches are refactoring preparing way for project
categories (for the next patch).
* [PATCH 6/6] gitweb: Optional grouping of projects by category
Port of Sebastien Cevey port of Sham Chukoury's patch for the XMMS2
gitweb to modern gitweb.
Shortlog:
~~~~~~~~~
Jakub Narebski (3):
gitweb: Restructure projects list generation
gitweb: Change the way "content tags" ('ctags') are handled
gitweb: Mark matched 'ctag' / contents tag (?by_tag=foo)
Sebastien Cevey (3):
gitweb: Split git_project_list_body in two functions
gitweb: Modularized git_get_project_description to be more generic
gitweb: Optional grouping of projects by category
Diffstat:
~~~~~~~~~
gitweb/README | 16 +
gitweb/gitweb.perl | 546 ++++++++++++++++++++---------
gitweb/static/gitweb.css | 7 +
t/t9500-gitweb-standalone-no-errors.sh | 57 +++
t/t9502-gitweb-standalone-parse-output.sh | 74 ++++
5 files changed, 542 insertions(+), 158 deletions(-)
--
1.7.3
next reply other threads:[~2011-04-29 17:52 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-29 17:51 Jakub Narebski [this message]
2011-04-29 17:51 ` [PATCH 1/6 (v2)] gitweb: Restructure projects list generation Jakub Narebski
2011-05-07 18:39 ` Jakub Narebski
2011-04-29 17:51 ` [PATCH 2/6] gitweb: Change the way "content tags" ('ctags') are handled Jakub Narebski
2011-04-29 17:51 ` [PATCH 3/6] gitweb: Mark matched 'ctag' / contents tag (?by_tag=foo) Jakub Narebski
2011-04-29 17:51 ` [PATCH 4/6] gitweb: Split git_project_list_body in two functions Jakub Narebski
2011-04-29 17:52 ` [PATCH 5/6] gitweb: Modularized git_get_project_description to be more generic Jakub Narebski
2011-04-29 17:52 ` [PATCH 6/6] gitweb: Optional grouping of projects by category Jakub Narebski
2011-04-29 21:31 ` [PATCH 0/6] gitweb: Improve ctags, introduce categories Junio C Hamano
2011-04-29 23:53 ` Jakub Narebski
2011-04-30 20:36 ` Øyvind A. Holm
2011-05-03 14:02 ` git-send-email and non 7bit clean message (was: [PATCH 0/6] gitweb: Improve ctags, introduce categories) Jakub Narebski
2011-05-04 13:50 ` [PATCH/RFC] git-send-email: Do not encode Subject if not required (was: git-send-email and non 7bit clean message) Jakub Narebski
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=1304099521-27617-1-git-send-email-jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=pasky@suse.cz \
--cc=seb@cine7.net \
--cc=u.kleine-koenig@pengutronix.de \
--cc=warthog9@eaglescrag.net \
--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).