From: Jakub Narebski <jnareb@gmail.com>
To: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Petr Baudis <pasky@suse.cz>
Subject: Re: [PATCHv8 1/7] gitweb: refactor author name insertion
Date: Tue, 30 Jun 2009 22:04:40 +0200 [thread overview]
Message-ID: <200906302204.40876.jnareb@gmail.com> (raw)
In-Reply-To: <1246312854-3365-2-git-send-email-giuseppe.bilotta@gmail.com>
On Tue, 30 Jun 2009, Giuseppe Bilotta wrote:
> Collect all author display code in appropriate functions, making it
> easier to extend these functions on the CGI side.
>
> We also move some of the presentation code from hard-coded HTML to CSS,
> for easier customization.
>
> A side effect of the refactoring is that now localtime is always
> displayed with the 'at night' warning.
It is a very nice side effect, I think.
>
> Signed-off-by: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
Acked-by: Jakub Narebski <jnareb@gmail.com>
> ---
> gitweb/gitweb.css | 5 ++-
> gitweb/gitweb.perl | 93 ++++++++++++++++++++++++++++++---------------------
> 2 files changed, 59 insertions(+), 39 deletions(-)
[...]
> +sub print_local_time {
> + my %date = @_;
> + if ($date{'hour_local'} < 6) {
> + printf(" (<span class=\"atnight\">%02d:%02d</span> %s)",
> + $date{'hour_local'}, $date{'minute_local'}, $date{'tz_local'});
> + } else {
> + printf(" (%02d:%02d %s)",
> + $date{'hour_local'}, $date{'minute_local'}, $date{'tz_local'});
> + }
> +}
Very nice refactoring.
It could do with a comment describing its output, but it is not
necessary, and IMHO not worth resend. We can always add it "in tree".
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2009-06-30 20:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 22:00 [PATCHv8 0/7] gitweb: avatar support Giuseppe Bilotta
2009-06-29 22:00 ` [PATCHv8 1/7] gitweb: refactor author name insertion Giuseppe Bilotta
2009-06-29 22:00 ` [PATCHv8 2/7] gitweb: uniform author info for commit and commitdiff Giuseppe Bilotta
2009-06-29 22:00 ` [PATCHv8 3/7] gitweb: use git_print_authorship_rows in 'tag' view too Giuseppe Bilotta
2009-06-29 22:00 ` [PATCHv8 4/7] gitweb: (gr)avatar support Giuseppe Bilotta
2009-06-29 22:00 ` [PATCHv8 5/7] gitweb: gravatar url cache Giuseppe Bilotta
2009-06-29 22:00 ` [PATCHv8 6/7] gitweb: picon avatar provider Giuseppe Bilotta
2009-06-29 22:00 ` [PATCHv8 7/7] gitweb: add empty alt text to avatar img Giuseppe Bilotta
2009-06-30 20:29 ` Jakub Narebski
2009-06-30 20:23 ` [PATCHv8 6/7] gitweb: picon avatar provider Jakub Narebski
2009-06-30 20:50 ` Giuseppe Bilotta
2009-06-30 20:18 ` [PATCHv8 5/7] gitweb: gravatar url cache Jakub Narebski
2009-06-30 20:38 ` Junio C Hamano
2009-06-30 20:52 ` Giuseppe Bilotta
2009-06-30 20:16 ` [PATCHv8 4/7] gitweb: (gr)avatar support Jakub Narebski
2009-06-30 20:10 ` [PATCHv8 3/7] gitweb: use git_print_authorship_rows in 'tag' view too Jakub Narebski
2009-06-30 20:04 ` [PATCHv8 2/7] gitweb: uniform author info for commit and commitdiff Jakub Narebski
2009-06-30 20:04 ` Jakub Narebski [this message]
2009-06-30 20:23 ` [PATCHv8 1/7] gitweb: refactor author name insertion Giuseppe Bilotta
2009-06-30 21:08 ` Jakub Narebski
2009-06-30 23:15 ` Giuseppe Bilotta
2009-07-01 7:41 ` 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=200906302204.40876.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=giuseppe.bilotta@gmail.com \
--cc=pasky@suse.cz \
/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).