From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Cc: Uwe Kleine-Koenig <u.kleine-koenig@pengutronix.de>,
Jonathan Nieder <jrnieder@gmail.com>, Petr Baudis <pasky@suse.cz>,
"J.H." <warthog9@kernel.org>, Sebastien Cevey <seb@cine7.net>,
Jakub Narebski <jnareb@gmail.com>
Subject: [RFC/PATCH 0/3] gitweb: Categories support
Date: Tue, 8 Mar 2011 00:13:32 +0100 [thread overview]
Message-ID: <1299539616-19991-1-git-send-email-jnareb@gmail.com> (raw)
This series is based on
"[PATCHv2/RFC] gitweb: Restructure projects list generation"
http://thread.gmane.org/gmane.comp.version-control.git/167996/focus=168321
http://repo.or.cz/w/git/jnareb-git.git/commit/420071752d13dcecd59e794d82285e7e142ef75f
('gitweb/web' branch in http://repo.or.cz/w/git/jnareb-git.git repository)
which is the main reason why this series is marked as an RFC.
This series is long in wait port of Sebastien Cevey series from
December 2008
http://thread.gmane.org/gmane.comp.version-control.git/102844
to modern gitweb. It was waiting for abovementioned restructuring of
projects list generation.
Uwe, it might be an alternative to use ctags (content tags, aka
project labels).
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
gitweb/README | 16 +++
gitweb/gitweb.perl | 166 +++++++++++++++++++++++---------
gitweb/static/gitweb.css | 7 ++
t/t9500-gitweb-standalone-no-errors.sh | 8 ++
4 files changed, 151 insertions(+), 46 deletions(-)
--
1.7.3
next reply other threads:[~2011-03-07 23:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 23:13 Jakub Narebski [this message]
2011-03-07 23:13 ` [PATCH 1/3] gitweb: Split git_project_list_body in two functions Jakub Narebski
2011-03-07 23:13 ` [PATCH 2/3] gitweb: Modularized git_get_project_description to be more generic Jakub Narebski
2011-03-07 23:13 ` [PATCH 3/3] gitweb: Optional grouping of projects by category 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=1299539616-19991-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@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).