From: Alex Riesen <raa.lkml@gmail.com>
To: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Use testlib to skip t3300-funny-names
Date: Thu, 5 Jan 2006 12:53:15 +0100 [thread overview]
Message-ID: <81b0412b0601050353o6b96ed4fp2a6d24dd514cc9c2@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 153 bytes --]
The test cannot be run on cygwin anyway.
Corrected the error message to reflect the problem source.
Signed-off-by: Alex Riesen <raa.lkml@gmail.com>
[-- Attachment #2: 0007-Use-testlib-to-skip-the-test-it-cannot-be-run-on-cygwin.txt --]
[-- Type: text/plain, Size: 1077 bytes --]
Subject: [PATCH] Use testlib to skip the test (it cannot be run on cygwin)
Correct the error message to reflect the problem source
Signed-off-by: Alex Riesen <raa.lkml@gmail.com>
---
t/t3300-funny-names.sh | 10 +++++++---
1 files changed, 7 insertions(+), 3 deletions(-)
721ca495bbbff1d387aa48ae401b7a14fb486ac0
diff --git a/t/t3300-funny-names.sh b/t/t3300-funny-names.sh
index 6a85d67..5d70594 100755
--- a/t/t3300-funny-names.sh
+++ b/t/t3300-funny-names.sh
@@ -9,11 +9,15 @@ This test tries pathnames with funny cha
tree, index, and tree objects.
'
-# since FAT/NTFS does not allow tabs in filenames, skip this test
-test "$(uname -o 2>/dev/null)" = Cygwin && exit 0
-
. ./test-lib.sh
+# Since FAT/NTFS does not allow tabs in filenames, skip this test.
+# Windows also have unexplainable problems with names containing only spaces.
+if [ "$(uname -o 2>/dev/null)" = Cygwin ]; then
+ say 'FAT and NTFS on Windows do not allow tabs in filenames, test skipped'
+ test_done
+fi
+
p0='no-funny'
p1='tabs ," (dq) and spaces'
p2='just space'
--
1.0.GIT
next reply other threads:[~2006-01-05 11:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-05 11:53 Alex Riesen [this message]
2006-01-06 22:38 ` Use testlib to skip t3300-funny-names Junio C Hamano
2006-01-07 9:25 ` Alex Riesen
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=81b0412b0601050353o6b96ed4fp2a6d24dd514cc9c2@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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).