git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jakub Narebski" <jnareb@gmail.com>
To: "David Rientjes" <rientjes@google.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] gitweb: Show project's git URL on summary page
Date: Tue, 15 Aug 2006 21:32:08 +0200	[thread overview]
Message-ID: <8fe92b430608151232y3f0ecd8ei435337709557162e@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0608151139280.29668@chino.corp.google.com>

On 8/15/06, David Rientjes <rientjes@google.com> wrote:
> On Tue, 15 Aug 2006, Jakub Narebski wrote:

> > +     my $is_first_url = 1;
> > +     foreach my $git_base_url (@git_base_url_list) {
> > +             next unless $git_base_url; # skip empty/zerolength URLs
> > +             print "<tr><td>";
> > +             if ($is_first_url) {
> > +                     print "URL";
> > +                     $is_first_url = 0;
> > +             }
> > +             print "</td><td>$git_base_url/$project</td></tr>\n";
> > +     }
>
> Isn't it faster to do this (over 1.4.2):
> +       my $url_tag = "URL";
> +       foreach my $git_base_url (@git_base_url_list) {
> +               next unless $git_base_url;
> +               print "<tr><td>$url_tag</td><td>$git_base_url/$project</td></tr>\n";
> +               $url_tag = "";
> +       }

Yes, it is undobtedly better.

Acked-by: Jakub Narebski <jnareb@gmail.com>

-- 
Jakub Narebski

  reply	other threads:[~2006-08-15 19:32 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-15 18:03 [PATCH] gitweb: Show project's git URL on summary page Jakub Narebski
2006-08-15 18:43 ` David Rientjes
2006-08-15 19:32   ` Jakub Narebski [this message]
2006-08-15 21:03 ` [PATCH (revised)] " Jakub Narebski
2006-08-15 21:36   ` David Rientjes
2006-08-16  7:31   ` Aneesh Kumar K.V
2006-08-16 12:56     ` Jakub Narebski
2006-08-16 12:50   ` [PATCH 2/2] gitweb: Add support for per project git URLs Jakub Narebski
2006-08-16 20:40     ` Junio C Hamano
2006-08-17  9:31       ` 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=8fe92b430608151232y3f0ecd8ei435337709557162e@mail.gmail.com \
    --to=jnareb@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=rientjes@google.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).