git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Thomas Singer <thomas.singer@syntevo.com>,
	Thomas Rast <trast@student.ethz.ch>,
	git@vger.kernel.org
Subject: Re: OS X and umlauts in file names
Date: Mon, 23 Nov 2009 15:31:52 -0800 (PST)	[thread overview]
Message-ID: <m3pr78bywe.fsf@localhost.localdomain> (raw)
In-Reply-To: <alpine.DEB.1.00.0911231916510.4897@intel-tinevez-2-302>

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

> On Mon, 23 Nov 2009, Thomas Singer wrote:
> 
> > Basically, getting it "somehow" to work on OS X is just one minor step. 
> > IMHO Git should standardize on file names in the repository and do the 
> > platform-specific conversion independent of any locale setting, if 
> > needed.
> 
> That is contrary to the design of Git which honors content (byte-wise!) as 
> much as possible, and treats file names very much as content.
> 
> There were beginnings of supporting OSX' brain-damaged filename mangling, 
> but an obnoxious OSX fan worked very hard on trying to defend the OSX 
> design and to decry Git's respect for the raw bytes on this list, so hard 
> that even the nicest developers had no fun working on this issue anymore.
> 
> This little background may help you understand why there is no solution 
> implemented in Git yet.  And maybe quite a few developers are reluctant to 
> discuss the issue and possible solutions due to said sad story, too.

To be more exact the problem is not that MacOS X uses denormalized
form (does file mangling).  This would be the problem only in
cross-platform development (where some developers would work from
different operating system).

The problem is that the name under which Git creates file is different
from the name MacOS X lists file (in readdir etc.).

-- 
Jakub Narebski
Poland
ShadeHawk on #git

  parent reply	other threads:[~2009-11-23 23:32 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-23 16:37 OS X and umlauts in file names Thomas Singer
2009-11-23 17:45 ` Thomas Rast
2009-11-23 18:10   ` Thomas Singer
2009-11-23 18:23     ` Johannes Schindelin
2009-11-23 20:31       ` Thomas Singer
2009-11-23 23:31       ` Jakub Narebski [this message]
2009-11-23 18:29     ` Martin Langhoff
2009-11-23 20:26 ` Daniel Barkalow
2009-11-25  8:50   ` Thomas Singer
2009-11-25  9:51     ` B Smith-Mannschott
2009-11-25 10:07     ` Martin Langhoff
2009-11-25 10:19       ` Martin Langhoff
2009-11-25 22:43     ` Andreas Schwab
2009-11-26  8:28       ` Thomas Singer
2009-11-26 17:27     ` Jay Soffian
2009-11-27 10:01       ` Thomas Singer
2009-11-27 10:20         ` Thomas Singer
2009-11-27 10:56           ` Martin Langhoff
2009-11-27 18:35             ` Thomas Singer
2009-11-26 17:23 ` Jay Soffian

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=m3pr78bywe.fsf@localhost.localdomain \
    --to=jnareb@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=thomas.singer@syntevo.com \
    --cc=trast@student.ethz.ch \
    /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).