Git development
 help / color / mirror / Atom feed
From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: Brian Gernhardt <benji@silverinsanity.com>
Cc: git@vger.kernel.org
Subject: Re: t9200-git-cvsexportcommit #8 failure on OS X
Date: Tue, 30 Jan 2007 23:20:00 +0100	[thread overview]
Message-ID: <200701302320.02187.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <20070130163219.GA14431@164.242.249.10.in-addr.arpa>

tisdag 30 januari 2007 17:32 skrev Brian Gernhardt:
[...]
> mkdir: ?: Invalid argument
>
> It looks like one of the odd characters that git's using for the test is
> an invalid character for HFS+, so the entire test fails.  Perhaps this
> should be made a "soft" failure like all of the SVN tests passing
> despite me not having SVN installed, or should a different character be
> used somewhere?  Git can't possibly be expected to work in a situation
> where the FS fails.

My fault. The problem is that the data is ISO-8859-1, which is invalid
when interpreted as UTF-8.  Another user reported the same problem in cygwin 
on a Korean Windows. The byte sequences are illegal there too.

A number of solution could be concieved, like converting to the local encoding 
first, but that cannot be done beacuase I couldn't find any non-ascii 
characters that would be convertible into any (major) locale. 

Another is to ignore the test if these files cannot be created.

-- robin

  reply	other threads:[~2007-01-30 22:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-30 16:32 t9200-git-cvsexportcommit #8 failure on OS X Brian Gernhardt
2007-01-30 22:20 ` Robin Rosenberg [this message]
2007-01-30 22:49 ` [PATCH] Fail softly if file system does not like test data Robin Rosenberg
2007-01-30 23:28   ` Brian Gernhardt
2007-01-31  0:14     ` Robin Rosenberg
2007-01-31  5:39       ` Brian Gernhardt
2007-01-31  0:10   ` Robin Rosenberg
2007-01-31 22:17     ` Junio C Hamano
2007-01-31 22:36       ` Robin Rosenberg

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=200701302320.02187.robin.rosenberg.lists@dewire.com \
    --to=robin.rosenberg.lists@dewire.com \
    --cc=benji@silverinsanity.com \
    --cc=git@vger.kernel.org \
    /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