From: Jakub Narebski <jnareb@gmail.com>
To: Kevin Ballard <kevin@sb.org>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] Make test script annotate-tests.sh handle missing authors
Date: Sat, 16 Oct 2010 00:34:58 -0700 (PDT) [thread overview]
Message-ID: <m3sk06617a.fsf@localhost.localdomain> (raw)
In-Reply-To: <1287208215-91901-1-git-send-email-kevin@sb.org>
Kevin Ballard <kevin@sb.org> writes:
> Also, I'm not a Perl programmer, so it's possible there's a better idiom
> for this sort of thing.
>
> t/annotate-tests.sh | 3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
>
> diff --git a/t/annotate-tests.sh b/t/annotate-tests.sh
> index 396b965..4e37a66 100644
> --- a/t/annotate-tests.sh
> +++ b/t/annotate-tests.sh
> @@ -9,6 +9,9 @@ check_count () {
> cat .result | perl -e '
> my %expect = (@ARGV);
> my %count = ();
> + while (my ($author, $count) = each %expect) {
> + $count{$author} = 0;
> + }
First, it is a very bad practice to have variables of different type
named the same way, here %count (hash) and $count (scalar, unused).
Perl idiom way would be
- my %count = ();
+ my %count = map { $_ => 0 } keys %expect;
> while (<STDIN>) {
> if (/^[0-9a-f]+\t\(([^\t]+)\t/) {
> my $author = $1;
> --
> 1.7.3.1.186.gc0af9.dirty
>
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2010-10-16 7:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-16 5:50 [PATCH] Make test script annotate-tests.sh handle missing authors Kevin Ballard
2010-10-16 7:34 ` Jakub Narebski [this message]
2010-10-16 10:43 ` Kevin Ballard
2010-10-16 11:09 ` [PATCH v2] Update test script annotate-tests.sh to handle missing/extra authors Kevin Ballard
2010-10-16 12:22 ` [PATCH] Make test script annotate-tests.sh handle missing authors 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=m3sk06617a.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kevin@sb.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).