From: Gustavo Sverzut Barbieri <barbieri@profusion.mobi>
To: git@vger.kernel.org
Cc: gitster@pobox.com, Gustavo Sverzut Barbieri <barbieri@profusion.mobi>
Subject: [PATCH 0/2] gitweb use sections
Date: Mon, 28 Jul 2008 23:34:26 -0300 [thread overview]
Message-ID: <1217298868-16513-1-git-send-email-barbieri@profusion.mobi> (raw)
The following two patches will add sections to gitweb so usability is
improved for large project listing. It looks like:
http://staff.get-e.org/
but it's a new code that also supports owner sort.
Patches orverview:
* [PATCH 1/2] gitweb: sort projects by path.
This one is required to fix project sort. Since we use paths, we
should compare individual components to make it look like a
tree. Since we now can enable sections this error will be more
evident, so there is the fix.
* [PATCH 2/2] gitweb: add section support to gitweb project listing.
The real section work. This will add use_sections variable and if
it evaluates to true sections will be enabled. Just project and
owner sections are implemented.
I hope it looks good for inclusion. Last time I did perl was about 8
years ago, please point any problems and I'll fix them.
--
Gustavo Sverzut Barbieri
http://profusion.mobi embedded systems
--------------------------------------
MSN: barbieri@gmail.com
Skype: gsbarbieri
Mobile: +55 (19) 9225-2202
next reply other threads:[~2008-07-29 2:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-29 2:34 Gustavo Sverzut Barbieri [this message]
2008-07-29 2:34 ` [PATCH 1/2] gitweb: sort projects by path Gustavo Sverzut Barbieri
2008-07-29 2:34 ` [PATCH 2/2] gitweb: add section support to gitweb project listing Gustavo Sverzut Barbieri
2008-07-29 3:59 ` [PATCH 1/2 v2] gitweb: sort projects by path Gustavo Sverzut Barbieri
2008-07-31 19:43 ` [PATCH 0/2] gitweb use sections Gustavo Sverzut Barbieri
2008-07-31 20:32 ` Petr Baudis
2008-07-31 20:58 ` Gustavo Sverzut Barbieri
2008-08-10 19:45 ` Gustavo Sverzut Barbieri
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=1217298868-16513-1-git-send-email-barbieri@profusion.mobi \
--to=barbieri@profusion.mobi \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).