From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Cc: Petr Baudis <pasky@suse.cz>, "J.H." <warthog19@eaglescrag.net>,
Frank Lichtenheld <frank@lichtenheld.de>,
Jakub Narebski <jnareb@gmail.com>
Subject: [PATCH 1/3] gitweb: Separate @projects population into git_get_projects_details()
Date: Mon, 17 Mar 2008 16:09:28 +0100 [thread overview]
Message-ID: <1205766570-13550-2-git-send-email-jnareb@gmail.com> (raw)
In-Reply-To: <1205766570-13550-1-git-send-email-jnareb@gmail.com>
From: Petr Baudis <pasky@suse.cz>
For clarity projects scanning and @projects population is separated to
git_get_projects_details().
This would be required if/when implementing in-gitweb caching of
projects list generation.
Signed-off-by: Petr Baudis <pasky@suse.cz>
Signed-off-by: Jakub Narebski <jnareb@gmail.com>
---
This is first part of patch sent by Petr Baudis; one that could be
applied to have better, more clear code, even as we are rehashing on
_how_ to do caching in gitweb in general, and projects list caching in
particular.
Note: git_get_projects_details() does not do
return wantarray ? @projects : \@projects
dance.
By the way; it could modify %$projlist directly, and return simply
$projlist.
gitweb/gitweb.perl | 17 +++++++++++++----
1 files changed, 13 insertions(+), 4 deletions(-)
diff --git a/gitweb/gitweb.perl b/gitweb/gitweb.perl
index ec73cb1..90ab894 100755
--- a/gitweb/gitweb.perl
+++ b/gitweb/gitweb.perl
@@ -3473,10 +3473,10 @@ sub git_patchset_body {
# . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
-sub git_project_list_body {
- my ($projlist, $order, $from, $to, $extra, $no_header) = @_;
-
- my ($check_forks) = gitweb_check_feature('forks');
+# fill age, description, owner, forks (last one only if $check_forks)
+# for all projects in $projlist reference; fill projects info
+sub git_get_projects_details {
+ my ($projlist, $check_forks) = @_;
my @projects;
foreach my $pr (@$projlist) {
@@ -3506,6 +3506,15 @@ sub git_project_list_body {
}
push @projects, $pr;
}
+ return @projects;
+}
+
+sub git_project_list_body {
+ my ($projlist, $order, $from, $to, $extra, $no_header) = @_;
+
+ my ($check_forks) = gitweb_check_feature('forks');
+
+ my @projects = git_get_projects_details($projlist, $check_forks);
$order ||= $default_projects_order;
$from = 0 unless defined $from;
--
1.5.4.3.453.gc1ad83
next prev parent reply other threads:[~2008-03-17 15:10 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-17 15:09 [PATCH 0/3 v2] gitweb: Support caching projects list Jakub Narebski
2008-03-17 15:09 ` Jakub Narebski [this message]
2008-03-17 15:09 ` [RFC/PATCH 2/3] " Jakub Narebski
2008-03-17 16:54 ` Frank Lichtenheld
2008-03-17 18:52 ` Jakub Narebski
2008-03-17 19:10 ` Frank Lichtenheld
2008-03-17 20:25 ` Jakub Narebski
2008-03-17 15:09 ` [RFC/PATCH 3/3] gitweb: Fill project details lazily when caching Jakub Narebski
2008-03-18 3:14 ` Petr Baudis
2008-03-18 9:12 ` Jakub Narebski
2008-03-18 9:52 ` Frank Lichtenheld
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=1205766570-13550-2-git-send-email-jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=frank@lichtenheld.de \
--cc=git@vger.kernel.org \
--cc=pasky@suse.cz \
--cc=warthog19@eaglescrag.net \
/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).