From: Jonathan Nieder <jrnieder@gmail.com>
To: Ben Walton <bdwalton@gmail.com>
Cc: gitster@pobox.com, dturner@twopensource.com, git@vger.kernel.org
Subject: Re: [PATCH] Use wc instead of awk to count subtrees in t0090-cache-tree
Date: Mon, 22 Dec 2014 14:01:17 -0800 [thread overview]
Message-ID: <20141222220117.GS29365@google.com> (raw)
In-Reply-To: <1419270744-1408-1-git-send-email-bdwalton@gmail.com>
Ben Walton wrote:
> echo "dir" | /usr/xpg4/bin/awk -v c=0 '$1 {++c} END {print c}'
> 0
Thanks. Weird. Does
awk -v c=0 '$1 != "" {++c} END {print c}'
work better?
[...]
> --- a/t/t0090-cache-tree.sh
> +++ b/t/t0090-cache-tree.sh
> @@ -22,7 +22,7 @@ generate_expected_cache_tree_rec () {
> # ls-files might have foo/bar, foo/bar/baz, and foo/bar/quux
> # We want to count only foo because it's the only direct child
> subtrees=$(git ls-files|grep /|cut -d / -f 1|uniq) &&
> - subtree_count=$(echo "$subtrees"|awk -v c=0 '$1 {++c} END {print c}') &&
> + subtree_count=$(echo "$subtrees"|wc -w) &&
> entries=$(git ls-files|wc -l) &&
> printf "SHA $dir (%d entries, %d subtrees)\n" "$entries" "$subtree_count" &&
Some implementations of wc add a trailing space, causing
printf: 1 : invalid number
Using
printf "SHA $dir (%d entries, %d subtrees)\n" "$entries" $subtree_count &&
(with no quotes around $subtree_count) would avoid trouble, though
that's a little subtle.
Hope that helps,
Jonathan
next prev parent reply other threads:[~2014-12-22 22:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-22 17:52 [PATCH] Use wc instead of awk to count subtrees in t0090-cache-tree Ben Walton
2014-12-22 21:45 ` Junio C Hamano
2014-12-22 22:02 ` Jonathan Nieder
2014-12-22 22:26 ` Junio C Hamano
2014-12-22 22:01 ` Jonathan Nieder [this message]
2014-12-22 23:25 ` Junio C Hamano
2014-12-22 23:27 ` Junio C Hamano
2014-12-22 23:38 ` Jonathan Nieder
2014-12-23 18:26 ` Junio C Hamano
2014-12-22 23:34 ` 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=20141222220117.GS29365@google.com \
--to=jrnieder@gmail.com \
--cc=bdwalton@gmail.com \
--cc=dturner@twopensource.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.