Git development
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: "Randal L. Schwartz" <merlyn@stonehenge.com>
Cc: Tarmigan <tarmigan+git@gmail.com>,
	"Shawn O. Pearce" <spearce@spearce.org>,
	git@vger.kernel.org
Subject: Re: OSX, ZFS, UTF8, git - somebody hates me in this list
Date: Mon, 5 May 2008 12:45:38 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.1.10.0805051240150.32269@woody.linux-foundation.org> (raw)
In-Reply-To: <86fxswa7ra.fsf@blue.stonehenge.com>



On Mon, 5 May 2008, Randal L. Schwartz wrote:
> 
> As I posted in a followup, without twiddling anything, ZFS on OSX
> is case *sensitive*, but apparently still "normalizes", which is causing
> the trip-up.  I'll look to see if there are any parameters I can tweak
> to keep it from doing that, but I doubt it.

Well, the good news is that while the utf-8 normalization is crazy, you're 
pretty unlikely to actually hit it in practice. The git archive has the 
Märchen file on purpose to find these kinds of issues, but it's harmless 
appart from the annoyance.

Yes, some projects will have i18n support that may have files with special 
characters on purpose, and they can cause problems. Not least exactly 
because OS X does all the normalization exactly the wrong way (ie it chose 
the _unusual_ way to do things, expanding strings to their longest format 
rather than their shortest format), but I would expect it to be very rare 
in general, partly because it doesn't really matter what SCM you use to 
track things, and you'll have similar issues if you ever develop anything 
across OS's.

We can fix it. Junio hasn't merged my stupid infrastructure into core git 
yet, and I still don't really care enough or have a OS X box to test on 
(I've got a couple of mac minis, but they run that other OS ;), but we'll 
get the insane OS X crap handled *some* day.

			Linus

  reply	other threads:[~2008-05-05 19:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-04 21:07 OSX, ZFS, UTF8, git - somebody hates me in this list Randal L. Schwartz
2008-05-04 21:52 ` Shawn O. Pearce
2008-05-04 21:56   ` Randal L. Schwartz
2008-05-04 22:00     ` Randal L. Schwartz
2008-05-05  6:52       ` David Brown
2008-05-05 10:33         ` Wincent Colaiuta
2008-05-04 22:04     ` Shawn O. Pearce
2008-05-04 22:06       ` Randal L. Schwartz
2008-05-04 22:15         ` Shawn O. Pearce
2008-05-05 17:39     ` Randal L. Schwartz
2008-05-05 17:53       ` Linus Torvalds
2008-05-05 19:00         ` Tarmigan
2008-05-05 19:08           ` Randal L. Schwartz
2008-05-05 19:45             ` Linus Torvalds [this message]
2008-05-06  8:48               ` Johannes Schindelin
2008-05-05 19:32           ` Mitch Tishmack

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=alpine.LFD.1.10.0805051240150.32269@woody.linux-foundation.org \
    --to=torvalds@linux-foundation.org \
    --cc=git@vger.kernel.org \
    --cc=merlyn@stonehenge.com \
    --cc=spearce@spearce.org \
    --cc=tarmigan+git@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