From: Jakub Narebski <jnareb@gmail.com>
To: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
Cc: Junio C Hamano <gitster@pobox.com>,
GIT Mailing-list <git@vger.kernel.org>,
marada@uwaterloo.ca
Subject: Re: [PATCH 06/14] t9501-*.sh: Fix a test failure on Cygwin
Date: Tue, 14 Dec 2010 20:04:28 +0100 [thread overview]
Message-ID: <201012142004.30322.jnareb@gmail.com> (raw)
In-Reply-To: <4D07B6DE.8080400@ramsay1.demon.co.uk>
Ramsay Jones wrote:
>
> The first (setup) test attempts to create a file, using the
> test_commit function, called 'i can has snapshot?'. On cygwin
> (and MinGW) this fails with a "No such file or directory" error.
> In order to fix the tests, we simply remove the '?' wildcard
> from the name, since the purpose of these tests is not about
> creating funny filenames.
>
> Signed-off-by: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
All right.
Acked-by: Jakub Narebski <jnareb@gmail.com>
BTW. if the test was about handling funny filenames (containing
leading, embedded and trailing space, +&@=<>"' characters), what
should we do instead?
> ---
> t/t9501-gitweb-standalone-http-status.sh | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/t/t9501-gitweb-standalone-http-status.sh b/t/t9501-gitweb-standalone-http-status.sh
> index 2487da1..18825af 100755
> --- a/t/t9501-gitweb-standalone-http-status.sh
> +++ b/t/t9501-gitweb-standalone-http-status.sh
> @@ -16,7 +16,7 @@ code and message.'
> # snapshot settings
>
> test_expect_success 'setup' "
> - test_commit 'SnapshotTests' 'i can has snapshot?'
> + test_commit 'SnapshotTests' 'i can has snapshot'
> "
>
>
> --
> 1.7.3
>
>
>
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2010-12-14 19:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-14 18:26 [PATCH 06/14] t9501-*.sh: Fix a test failure on Cygwin Ramsay Jones
2010-12-14 19:04 ` Jakub Narebski [this message]
2010-12-16 19:25 ` Ramsay Jones
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=201012142004.30322.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=marada@uwaterloo.ca \
--cc=ramsay@ramsay1.demon.co.uk \
/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).