From: Jakub Narebski <jnareb@gmail.com>
To: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH 7/7] gitweb: group remote heads
Date: Fri, 17 Sep 2010 18:54:03 +0200 [thread overview]
Message-ID: <201009171854.03476.jnareb@gmail.com> (raw)
In-Reply-To: <1284629465-14798-8-git-send-email-giuseppe.bilotta@gmail.com>
On Thu, 16 Sep 2010, Giuseppe Bilotta wrote:
> diff --git a/gitweb/gitweb.perl b/gitweb/gitweb.perl
> index 92551e4..66b5400 100755
> --- a/gitweb/gitweb.perl
> +++ b/gitweb/gitweb.perl
> @@ -2758,6 +2758,16 @@ sub git_get_last_activity {
> return (undef, undef);
> }
>
> +sub git_get_remotes {
> + my ($limit) = @_;
Probably more Perl-ish way would be to use
+ my $limit = shift;
but this version is also all right.
> + open my $fd, '-|' , git_cmd(), 'remote';
> + return () unless $fd;
Gitweb usualy uses
+ open my $fd, '-|' , git_cmd(), 'remote';
+ or return;
> + my @remotes = map { chomp ; $_ } <$fd>;
About Ævar comment: while
+ chomp(my @remotes = <$fd>);
might be more Perl-ish, the above syntax is used thorough gitweb code.
So I'd leave it as it is now as the matter of code consistency.
> + close $fd or return ();
+ close $fd or return;
> + my @remoteheads = git_get_heads_list($limit, 'remotes');
> + return (\@remotes, \@remoteheads);
Why do you want for git_get_remotes() to also return remote-tracking
branches (refs/remotes/)? Those are separate issues, and I think it
would be better API for git_get_remotes() to provide only list of
remotes, i.e.
+ return @remotes;
Especially that we might want in the summary view to only list remotes,
without listing remote-tracking branches.
That would require more changes to the code.
> +}
> +
> sub git_get_references {
> my $type = shift || "";
> my %refs;
> @@ -4979,7 +4989,7 @@ sub git_heads_body {
> "<td class=\"link\">" .
> $cgi->a({-href => href(action=>"shortlog", hash=>$ref{'fullname'})}, "shortlog") . " | " .
> $cgi->a({-href => href(action=>"log", hash=>$ref{'fullname'})}, "log") . " | " .
> - $cgi->a({-href => href(action=>"tree", hash=>$ref{'fullname'}, hash_base=>$ref{'name'})}, "tree") .
> + $cgi->a({-href => href(action=>"tree", hash=>$ref{'fullname'}, hash_base=>$ref{'fullname'})}, "tree") .
This is independent change, and should be in a separate commit, isn't it?
> "</td>\n" .
> "</tr>";
> }
> @@ -4991,6 +5001,19 @@ sub git_heads_body {
> print "</table>\n";
> }
>
> +sub git_remotes_body {
> + my ($remotedata, $head) = @_;
> + my @remotenames = @{$remotedata->[0]};
> + my @allheads = @{$remotedata->[1]};
Why not
+ my ($remotenames, $allheads, $head) = @_;
Beside, isn't it $remote_heads and not $allheads?
> + foreach my $remote (@remotenames) {
It would be then
+ foreach my $remote (@$remotenames) {
> + my @remoteheads = grep { $_->{'name'} =~ s!^\Q$remote\E/!! } @allheads;
Should we display remote even if it doesn't have any remote heads
associated with it?
> + git_begin_group("remotes", $remote, "remotes/$remote",$remote);
> + git_heads_body(\@remoteheads, $head);
> + git_end_group();
This would have to be modified with change to git_begin_group() /
/ git_end_group().
BTW isn't it premature generalization? It is only place AFAIKS that
uses git_*_group() subroutines.
> + }
> +
> +}
> +
> sub git_search_grep_body {
> my ($commitlist, $from, $to, $extra) = @_;
> $from = 0 unless defined $from;
> @@ -5137,7 +5160,7 @@ sub git_summary {
> # there are more ...
> my @taglist = git_get_tags_list(16);
> my @headlist = git_get_heads_list(16, 'heads');
> - my @remotelist = $remote_heads ? git_get_heads_list(16, 'remotes') : ();
> + my @remotelist = $remote_heads ? git_get_remotes(16) : ();
No change of git_get_remotes() does only one thing: returning list
of remotes.
> my @forklist;
> my $check_forks = gitweb_check_feature('forks');
>
> @@ -5217,9 +5240,7 @@ sub git_summary {
>
> if (@remotelist) {
> git_print_header_div('remotes');
> - git_heads_body(\@remotelist, $head, 0, 15,
> - $#remotelist <= 15 ? undef :
> - $cgi->a({-href => href(action=>"remotes")}, "..."));
> + git_remotes_body(\@remotelist, $head);
Calling convention would change with my proposed change.
We might want to print only list of remotes (perhaps with number of
tracked branches) in the 'summary' view. Just an idea...
> }
>
> if (@forklist) {
> @@ -5551,9 +5572,9 @@ sub git_remotes {
> git_print_page_nav('','', $head,undef,$head, $heads_nav);
> git_print_header_div('summary', $project);
>
> - my @remotelist = git_get_heads_list(undef, 'remotes');
> + my @remotelist = git_get_remotes();
> if (@remotelist) {
> - git_heads_body(\@remotelist, $head);
> + git_remotes_body(\@remotelist, $head);
Same here.
> }
> git_footer_html();
> }
> --
> 1.7.3.rc1.230.g8b572
>
>
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2010-09-17 16:54 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-16 9:30 [PATCH 0/7] gitweb: allheads feature Giuseppe Bilotta
2010-09-16 9:30 ` [PATCH 1/7] gitweb: introduce remote_heads feature Giuseppe Bilotta
2010-09-16 21:41 ` Jakub Narebski
2010-09-17 15:39 ` Giuseppe Bilotta
2010-09-16 9:31 ` [PATCH 2/7] gitweb: git_get_heads_list accepts an optional list of refs Giuseppe Bilotta
2010-09-16 22:14 ` Jakub Narebski
2010-09-17 15:52 ` Giuseppe Bilotta
2010-09-16 9:31 ` [PATCH 3/7] gitweb: separate heads and remotes lists Giuseppe Bilotta
2010-09-16 10:19 ` Ævar Arnfjörð Bjarmason
2010-09-16 11:35 ` Giuseppe Bilotta
2010-09-16 22:30 ` Jakub Narebski
2010-09-16 22:54 ` Ævar Arnfjörð Bjarmason
2010-09-16 22:46 ` Jakub Narebski
2010-09-16 9:31 ` [PATCH 4/7] gitweb: link heads and remotes view Giuseppe Bilotta
2010-09-16 23:02 ` Jakub Narebski
2010-09-17 16:01 ` Giuseppe Bilotta
2010-09-16 9:31 ` [PATCH 5/7] gitweb: auxiliary functions to group data Giuseppe Bilotta
2010-09-16 10:26 ` Ævar Arnfjörð Bjarmason
2010-09-17 1:24 ` Jakub Narebski
2010-09-17 6:54 ` Giuseppe Bilotta
2010-09-17 16:06 ` Jakub Narebski
2010-09-17 16:41 ` Giuseppe Bilotta
2010-09-17 17:17 ` Jakub Narebski
2010-09-18 7:51 ` Giuseppe Bilotta
2010-09-16 9:31 ` [PATCH 6/7] gitweb: group styling Giuseppe Bilotta
2010-09-17 16:26 ` Jakub Narebski
2010-09-17 16:49 ` Giuseppe Bilotta
2010-09-17 17:22 ` Jakub Narebski
2010-09-16 9:31 ` [PATCH 7/7] gitweb: group remote heads Giuseppe Bilotta
2010-09-16 10:29 ` Ævar Arnfjörð Bjarmason
2010-09-16 11:36 ` Giuseppe Bilotta
2010-09-17 16:54 ` Jakub Narebski [this message]
2010-09-17 17:25 ` Jakub Narebski
2010-09-19 5:39 ` Giuseppe Bilotta
2010-09-19 23:02 ` Jakub Narebski
2010-09-20 8:15 ` Giuseppe Bilotta
2010-09-20 8:59 ` Jakub Narebski
2010-09-20 9:38 ` Giuseppe Bilotta
2010-09-22 8:34 ` Jakub Narebski
2010-09-22 9:34 ` Giuseppe Bilotta
2010-09-16 21:26 ` [PATCH 0/7] gitweb: allheads feature Jakub Narebski
2010-09-17 7:24 ` Giuseppe Bilotta
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=201009171854.03476.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=giuseppe.bilotta@gmail.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).