From: Martin Langhoff <martin.langhoff@gmail.com>
To: Thomas Singer <thomas.singer@syntevo.com>
Cc: Daniel Barkalow <barkalow@iabervon.org>, git@vger.kernel.org
Subject: Re: OS X and umlauts in file names
Date: Wed, 25 Nov 2009 11:19:56 +0100 [thread overview]
Message-ID: <46a038f90911250219p54badb6era2177e2f6484f6d9@mail.gmail.com> (raw)
In-Reply-To: <46a038f90911250207o214b3952s67a022a017dbe2d9@mail.gmail.com>
On Wed, Nov 25, 2009 at 11:07 AM, Martin Langhoff
<martin.langhoff@gmail.com> wrote:
> On Wed, Nov 25, 2009 at 9:50 AM, Thomas Singer
> <thomas.singer@syntevo.com> wrote:
>> toms-mac-mini:git-umlauts tom$ git stage "U\314\210berla\314\210nge.txt"
>> fatal: pathspec 'U\314\210berla\314\210nge.txt' did not match any files
>
> does a find * | xargs git add work?
Also, you can try with `find * -print0 | git-update-index --add
--stdin -z `. Find should report the exact filename that the OS has,
and git should add it as it is.
Background: git-add used to be a trivial shell script wrapping around
git-update-index. If you have a git checkout, try:
git show f25933987f29070e9cd79dfddf03018010e82e80:git-add.sh
If git cannot track this file in a pure OSX world, there is a good
chance it's a bug in git.
In in this narrow test case (single machine, running OSX) git *must*
be able to do the right thing. If you work on multi-platform projects
however, there is a good chance a Windows or Linux user will commit a
file with a name that _when you checkout on OSX_, OSX will save with a
different (but "equivalent") name due to its funny decomposition
rules. And all sorts of "fun" will ensue.
cheers,
m
--
martin.langhoff@gmail.com
martin@laptop.org -- School Server Architect
- ask interesting questions
- don't get distracted with shiny stuff - working code first
- http://wiki.laptop.org/go/User:Martinlanghoff
next prev parent reply other threads:[~2009-11-25 10:20 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
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 [this message]
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=46a038f90911250219p54badb6era2177e2f6484f6d9@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=thomas.singer@syntevo.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;
as well as URLs for NNTP newsgroup(s).