Re: OS X and umlauts in file names
- From
Martin Langhoff <martin.langhoff@gmail.com>
- Date
- Nov 25, 2009, 10:19 UTC
- Message-ID
- <46a038f90911250219p54badb6era2177e2f6484f6d9@mail.gmail.com>
- In-Reply-To
- <46a038f90911250207o214b3952s67a022a017dbe2d9@mail.gmail.com>
On Wed, Nov 25, 2009 at 11:07 AM, Martin Langhoff <martin.langhoff@gmail.com> wrote:
Show 6 quoted lines
> 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