From: Jeff King <peff@peff.net>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: git@vger.kernel.org, Johannes Sixt <j6t@kdbg.org>,
Don Slutz <Don.Slutz@SierraAtlantic.com>
Subject: Re: [PATCH 1/3] test-lib: tests can have multiple prerequisites
Date: Mon, 26 Apr 2010 15:17:03 -0400 [thread overview]
Message-ID: <20100426191703.GC10772@coredump.intra.peff.net> (raw)
In-Reply-To: <20100421133806.GA5595@progeny.tock>
On Wed, Apr 21, 2010 at 08:38:06AM -0500, Jonathan Nieder wrote:
> Alas, I didn’t notice the thread with the almost identical patch [1]
> before writing this one.
>
> Since I am painting it, I prefer this way. I find it intuitive and
> can’t really see where the fuss about using some other coding style
> came from. So I would be very happy if someone who does understand
> the fuss could come up with a comment to add to the commit message
> about this. :)
I liked commas better, but since you are doing the work of writing the
patches, I will let it go. :)
I do wonder if it might be less error-prone to have:
test_expect_success PREREQ1 PREREQ2 'desc' 'test'
instead of
test_expect_success 'PREREQ1 PREREQ2' 'desc' 'test'
which should just be something like
while test $# -gt 2; do
test_have_prereq "$1" || skip=t
shift
done
But if you think that's dumb, just ignore it. It is really not worth
spending that much time on.
-Peff
next prev parent reply other threads:[~2010-04-26 19:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-21 13:12 [PATCH 0/3] running tests as fakeroot Jonathan Nieder
2010-04-21 13:38 ` [PATCH 1/3] test-lib: tests can have multiple prerequisites Jonathan Nieder
2010-04-21 14:57 ` Jonathan Nieder
2010-04-26 19:17 ` Jeff King [this message]
2010-04-27 0:06 ` Junio C Hamano
2010-04-27 1:25 ` Jeff King
2010-04-21 13:44 ` [PATCH 2/3] t1004 (read-tree): the unremovable symlink test requires POSIXPERM Jonathan Nieder
2010-04-21 14:20 ` [PATCH 3/3] Permit tests to be run as a (fake) root user Jonathan Nieder
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=20100426191703.GC10772@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=Don.Slutz@SierraAtlantic.com \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.org \
--cc=jrnieder@gmail.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 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).