From: Junio C Hamano <gitster@pobox.com>
To: Adam Roben <aroben@apple.com>
Cc: git@vger.kernel.org, Johannes Sixt <j.sixt@viscovery.net>
Subject: Re: [PATCH 01/11] Add tests for git cat-file
Date: Fri, 25 Apr 2008 11:03:43 -0700 [thread overview]
Message-ID: <7vve25q0ao.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: 1208978273-98146-2-git-send-email-aroben@apple.com
Adam Roben <aroben@apple.com> writes:
> Signed-off-by: Adam Roben <aroben@apple.com>
> ---
> t/t1006-cat-file.sh | 101 +++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 files changed, 101 insertions(+), 0 deletions(-)
> create mode 100755 t/t1006-cat-file.sh
>
> diff --git a/t/t1006-cat-file.sh b/t/t1006-cat-file.sh
> new file mode 100755
> index 0000000..15741d9
> --- /dev/null
> +++ b/t/t1006-cat-file.sh
> @@ -0,0 +1,101 @@
> +#!/bin/sh
> +
> +test_description='git cat-file'
> +
> +. ./test-lib.sh
> +
> +function echo_without_newline()
> +{
> + echo "$@\c"
> +}
"function " noiseword is unnecessary and unportable.
echo "\c" is unportable. Traditional trick to do this is to pipe it to tr
to strip "\010".
When you see "<anything>$@<anything>" in shell scripts, you usually do not
mean it, but instead mean "<anything>$*<anything>". It does not make
difference if you always feed a single parameter, but it is a good habit
to get into.
> +function maybe_remove_timestamp()
> +{
> + if test -z "$2"; then
> + echo_without_newline "$1"
> + else
> + echo_without_newline "$1" | sed -e 's/ [0-9]\{10\} [+-][0-9]\{4\}$//'
We tend to avoid \{num\| for portability. Do you really need them here?
> +function run_tests()
> +{
> + type=$1
> + sha1=$2
> + size=$3
> + content=$4
> + pretty_content=$5
> + no_timestamp=$6
> +
> + test_expect_success \
> + "$type exists" \
> + "git cat-file -e $sha1"
> + test_expect_success \
> + "Type of $type is correct" \
> + "test $type = \"\$(git cat-file -t $sha1)\""
It is quite hard to read with backslashes inside dq. Please use single
quote pairs without excess backslashes when possible.
next prev parent reply other threads:[~2008-04-25 18:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-23 19:17 Speed up git-svn fetch Adam Roben
2008-04-23 19:17 ` [PATCH 01/11] Add tests for git cat-file Adam Roben
2008-04-23 19:17 ` [PATCH 02/11] git-cat-file: Small refactor of cmd_cat_file Adam Roben
2008-04-23 19:17 ` [PATCH 03/11] git-cat-file: Make option parsing a little more flexible Adam Roben
2008-04-23 19:17 ` [PATCH 04/11] git-cat-file: Add --batch-check option Adam Roben
2008-04-23 19:17 ` [PATCH 05/11] git-cat-file: Add --batch option Adam Roben
2008-04-23 19:17 ` [PATCH 06/11] Move git-hash-object tests from t5303 to t1007 Adam Roben
2008-04-23 19:17 ` [PATCH 07/11] Add more tests for git hash-object Adam Roben
2008-04-23 19:17 ` [PATCH 08/11] git-hash-object: Add --stdin-paths option Adam Roben
2008-04-23 19:17 ` [PATCH 09/11] Git.pm: Add command_bidi_pipe and command_close_bidi_pipe Adam Roben
2008-04-23 19:17 ` [PATCH 10/11] Git.pm: Add hash_and_insert_object and cat_blob Adam Roben
2008-04-23 19:17 ` [PATCH 11/11] git-svn: Speed up fetch Adam Roben
2008-04-25 18:04 ` [PATCH 03/11] git-cat-file: Make option parsing a little more flexible Junio C Hamano
2008-04-25 6:56 ` [PATCH 01/11] Add tests for git cat-file Eric Wong
2008-04-25 18:06 ` Junio C Hamano
2008-04-25 18:03 ` Junio C Hamano [this message]
2008-05-06 6:41 ` Junio C Hamano
2008-04-23 19:19 ` Speed up git-svn fetch Adam Roben
2008-04-25 7:15 ` Eric Wong
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=7vve25q0ao.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=aroben@apple.com \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
/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).