git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: "Randal L. Schwartz" <merlyn@stonehenge.com>
Cc: git@vger.kernel.org
Subject: Re: OSX, ZFS, UTF8, git - somebody hates me in this list
Date: Sun, 4 May 2008 18:04:25 -0400	[thread overview]
Message-ID: <20080504220425.GI29038@spearce.org> (raw)
In-Reply-To: <86skwxd97d.fsf@blue.stonehenge.com>

"Randal L. Schwartz" <merlyn@stonehenge.com> wrote:
> >> 
> >> # On branch master
> >> # Untracked files:
> >> #   (use "git add <file>..." to include in what will be committed)
> >> #
> >> #       "gitweb/test/Ma\314\210rchen"
> >> nothing added to commit but untracked files present (use "git add" to track)
> 
> Shawn> Isn't this just the normal HFS+ name mangling?
> 
> I don't recall having this problem on HFS+.

Everyone has this problem on HFS+.  :-|
 
> But, oh, it's because my git.git is on a UFS partition.  So UFS works
> fine.  Why shouldn't ZFS (which will be closer to UFS than HFS+)
> be the same?

Because Apple is Apple and things must be done The Apple Way(tm),
or no black turtleneck for you?

-- 
Shawn.

  parent reply	other threads:[~2008-05-04 22:05 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 [this message]
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
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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080504220425.GI29038@spearce.org \
    --to=spearce@spearce.org \
    --cc=git@vger.kernel.org \
    --cc=merlyn@stonehenge.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).