git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: git@vger.kernel.org
Cc: "Junio C Hamano" <gitster@pobox.com>,
	"Jonathan Nieder" <jrnieder@gmail.com>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Subject: [PATCH v2 0/5] Skip tests using 3-arg test_*
Date: Wed, 28 Jul 2010 10:34:54 +0000	[thread overview]
Message-ID: <1280313299-721-1-git-send-email-avarab@gmail.com> (raw)

This is just like v1 aside from:
    
    diff --git a/t/t4004-diff-rename-symlink.sh b/t/t4004-diff-rename-symlink.sh
    index 85a77b3..92a65f4 100755
    --- a/t/t4004-diff-rename-symlink.sh
    +++ b/t/t4004-diff-rename-symlink.sh
    @@ -38 +38 @@ test_expect_success SYMLINKS 'setup diff output' "
    -    GIT_DIFF_OPTS=--unified=0 git diff-index -M -p $tree >current
    +    GIT_DIFF_OPTS=--unified=0 git diff-index -M -p $tree >current &&

But I also split the change I made to t/t4004-diff-rename-symlink.sh
from the "tests: implicitly skip SYMLINKS tests using <prereq>" patch
as suggested by Jonathan Nieder.

It was the only one in the aforementioned commit that didn't just nuke
skip_all=* + do 's/success /success SYMLINKS /', so it deserved a
separate patch.
    
Ævar Arnfjörð Bjarmason (5):
  tests: implicitly skip SYMLINKS tests using <prereq>
  t/t4004-diff-rename-symlink.sh: use three-arg <prereq>
  t/t5800-remote-helpers.sh: Skip with prereq on python <2.4
  t/t7800-difftool.sh: Skip with prereq on no PERL
  t/README: Update "Skipping tests" to align with best practices

 t/README                          |   21 +++++++++++++--
 t/t2007-checkout-symlink.sh       |   14 +++-------
 t/t4004-diff-rename-symlink.sh    |   18 +++++--------
 t/t4011-diff-symlink.sh           |   18 ++++---------
 t/t4023-diff-rename-typechange.sh |   14 +++-------
 t/t4114-apply-typechange.sh       |   28 ++++++++-------------
 t/t4115-apply-symlink.sh          |   12 ++-------
 t/t4122-apply-symlink-inside.sh   |   12 ++-------
 t/t5522-pull-symlink.sh           |   14 +++-------
 t/t5800-remote-helpers.sh         |   24 ++++++++----------
 t/t6035-merge-dir-to-symlink.sh   |   20 +++++----------
 t/t7800-difftool.sh               |   49 ++++++++++++++++--------------------
 12 files changed, 100 insertions(+), 144 deletions(-)

             reply	other threads:[~2010-07-28 10:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-28 10:34 Ævar Arnfjörð Bjarmason [this message]
2010-07-28 10:34 ` [PATCH v2 1/5] tests: implicitly skip SYMLINKS tests using <prereq> Ævar Arnfjörð Bjarmason
2010-07-29  1:00   ` Jonathan Nieder
2010-07-28 10:34 ` [PATCH v2 2/5] t/t4004-diff-rename-symlink.sh: use three-arg <prereq> Ævar Arnfjörð Bjarmason
2010-07-29  1:09   ` Jonathan Nieder
2010-07-29  1:56     ` Ævar Arnfjörð Bjarmason
2010-07-28 10:34 ` [PATCH v2 3/5] t/t5800-remote-helpers.sh: Skip with prereq on python <2.4 Ævar Arnfjörð Bjarmason
2010-07-29  1:16   ` Jonathan Nieder
2010-07-29  2:03     ` Ævar Arnfjörð Bjarmason
2010-07-28 10:34 ` [PATCH v2 4/5] t/t7800-difftool.sh: Skip with prereq on no PERL Ævar Arnfjörð Bjarmason
2010-07-28 10:34 ` [PATCH v2 5/5] t/README: Update "Skipping tests" to align with best practices Ævar Arnfjörð Bjarmason

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=1280313299-721-1-git-send-email-avarab@gmail.com \
    --to=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --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).