From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Cc: Lea Wiemann <LeWiemann@gmail.com>
Subject: [PATCH 0/2] gitweb: Refactor projects_list generation
Date: Tue, 10 Jun 2008 19:19:23 +0200 [thread overview]
Message-ID: <200806101919.24242.jnareb@gmail.com> (raw)
These two patches make code generating 'projects_list" view better.
This is resend of those patches, this time without following patches
which add new features like allowing 'description' field in
$projects_list file, searching for projects, and paginating projects
list page.
Those two patches should also make it easier for Lea to plug-in
caching in gitweb. That's why I'm sending them even in the rc/freeze
period...
Shortlog:
=========
Jakub Narebski (2):
gitweb: Separate filling list of projects info
gitweb: Separate generating 'sort by' table header
Diffstat:
=========
gitweb/gitweb.perl | 111 +++++++++++++++++++++++++++++-----------------------
1 files changed, 62 insertions(+), 49 deletions(-)
--
Jakub Narebski
ShadeHawk on #git
next reply other threads:[~2008-06-10 17:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-10 17:19 Jakub Narebski [this message]
2008-06-10 17:21 ` [PATCH 1/2] gitweb: Separate filling list of projects info Jakub Narebski
2008-06-10 17:21 ` [PATCH 2/2] gitweb: Separate generating 'sort by' table header 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=200806101919.24242.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=LeWiemann@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).