From: Andreas Schwab <schwab@linux-m68k.org>
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 23:43:54 +0100 [thread overview]
Message-ID: <m21vjmkyxh.fsf@igel.home> (raw)
In-Reply-To: <4B0CEFCA.5020605@syntevo.com> (Thomas Singer's message of "Wed, 25 Nov 2009 09:50:18 +0100")
Thomas Singer <thomas.singer@syntevo.com> writes:
> I've did following:
>
> toms-mac-mini:git-umlauts tom$ ls
> Überlänge.txt
> toms-mac-mini:git-umlauts tom$ git status
> # On branch master
> #
> # Initial commit
> #
> # Changes to be committed:
> # (use "git rm --cached <file>..." to unstage)
> #
> # new file: "U\314\210berla\314\210nge.txt"
> #
> 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
Try $'U\314\210berla\314\210nge.txt' instead.
"U\314\210berla\314\210nge.txt" is the same as
"U\\314\\210berla\\314\\210nge.txt" to the shell.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2009-11-25 22:44 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
2009-11-25 22:43 ` Andreas Schwab [this message]
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=m21vjmkyxh.fsf@igel.home \
--to=schwab@linux-m68k.org \
--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).