From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] gitweb: Add local time and timezone to git_print_authorship
Date: Tue, 29 Aug 2006 10:23:39 +0200 [thread overview]
Message-ID: <ed0ths$okn$1@sea.gmane.org> (raw)
In-Reply-To: 7vveocpfa3.fsf@assigned-by-dhcp.cox.net
Junio C Hamano wrote:
> Jakub Narebski <jnareb@gmail.com> writes:
>
>> Add local time (hours and minutes) and local timezone to the output of
>> git_print_authorship command, used by git_commitdiff.
>
> Looks nice, thanks.
>
> Now I got envious seeing people are having SO MUCH FUN with
> gitweb, so here is mine...
>
> Likes, dislikes, "your color selection sucks ;-)",... ?
>
> -- >8 --
> +td.age-week { color: #00f; background-color: #fff; }
> +td.age-month { color: #00f; background-color: #eef; }
> +td.age-season { color: #00f; background-color: #ddf; }
> +td.age-year { color: #00f; background-color: #ccf; }
> +td.age-old { color: #00f; background-color: #bbf; }
Could you use full hex color length? Everywhere else in CSS we use
6-char wide hex colours.
> + my $now = time();
> while (<$fd>) {
> - /^([0-9a-fA-F]{40}).*?(\d+)\)\s{1}(\s*.*)/;
> - my $full_rev = $1;
> + my ($full_rev, $author, $timestamp, $zone, $lineno, $data) =
> + /^([0-9a-fA-F]{40})\s\((.*?)\s+(\d+)\s
> + ([-+\d]{5})\s+(\d+)\)\s{1}(\s*.*)/x;
Nice compact style. But different from other parsing using regexp in gitweb.
And some of those other, e.g. parse_difftree_raw_line cannot use this style.
Doesn't matter much.
> my $rev = substr($full_rev, 0, 8);
> - my $lineno = $2;
> - my $data = $3;
> +
> + my $age = $now - $timestamp;
> + my $ago = age_string($age);
> + my $pop = "$author, $ago";
> + my $agegroup =
> + (($age < 60*60*24*7) ? "age-week" :
> + ($age < 60*60*24*30) ? "age-month" :
> + ($age < 60*60*24*120) ? "age-season" :
> + ($age < 60*60*24*360) ? "age-year" : "age-old");
We have age_class subroutine which does something similar.
I'm not sure if one subroutine can be used for those two situations.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2006-08-29 8:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-28 12:48 [PATCH 0/5] gitweb: Additions to commitdiff view Jakub Narebski
2006-08-28 12:48 ` [PATCH 1/5] gitweb: Make git_print_log generic; git_print_simplified_log uses it Jakub Narebski
2006-08-28 12:48 ` [PATCH 2/5] gitweb: Do not remove signoff lines in git_print_simplified_log Jakub Narebski
2006-08-28 12:48 ` [PATCH 3/5] gitweb: Add author information to commitdiff view Jakub Narebski
2006-08-28 12:48 ` [PATCH 4/5] gitweb: git_print_log: signoff line is non-empty line Jakub Narebski
2006-08-28 12:48 ` [PATCH 5/5] gitweb: Add diff tree, with links to patches, to commitdiff view Jakub Narebski
2006-08-28 17:26 ` [PATCH 0/5] gitweb: Additions " Linus Torvalds
2006-08-28 21:17 ` [PATCH] gitweb: Add local time and timezone to git_print_authorship Jakub Narebski
2006-08-29 0:16 ` Junio C Hamano
2006-08-29 8:23 ` Jakub Narebski [this message]
2006-08-29 9:05 ` Junio C Hamano
2006-08-29 10:15 ` Jakub Narebski
2006-08-30 4:26 ` Junio C Hamano
2006-08-30 9:47 ` Jakub Narebski
2006-08-29 9:06 ` [PATCH] gitweb: split output routine of blame2 Junio C Hamano
2006-08-29 9:06 ` [PATCH] gitweb: show rev only on the first line of each group in blame Junio C Hamano
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='ed0ths$okn$1@sea.gmane.org' \
--to=jnareb@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).