From: "Tajti Ákos" <akos.tajti@intland.com>
To: Alexey Shumkin <zapped@mail.ru>
Cc: Jonathan Nieder <jrnieder@gmail.com>, git@vger.kernel.org
Subject: Re: Special characters in file name
Date: Mon, 05 Sep 2011 14:14:53 +0200 [thread overview]
Message-ID: <4E64BD3D.6060900@intland.com> (raw)
In-Reply-To: <20110904000933.195d5bf4@zappedws>
Thanks four your answer. However, it didn't help. After setting the
core.quotepath option to false I get this:
diff --git a/<E1>rv<ED>zt<FB>r<F5> b/<E1>rv<ED>zt<FB>r<F5>
Is there a solution?
Thanks,
Ákos Tajti
2011.09.03. 22:09 keltezéssel, Alexey Shumkin írta:
>> Hi Alexey,
>>
>> Alexey Shumkin wrote:
>>> Tajti Ákos writes:
>>>> I have a file named "árvíz.txt" in my repository. When modify that
>>>> file and execute git diff, the first line looks like this:
>>>> diff --git "a/\303\241rv\303\255z.txt" "b/\303\241rv\303\255z.txt"
>>>>
>>>> Is there an option that (if specified) will get git to print
>>>> "árvíz.txt" instead of this escaped string?
>> [...]
>>> please, refresh your memory )))
>>> http://comments.gmane.org/gmane.comp.version-control.git/177849
>>>
>>> see my comment
>>> http://permalink.gmane.org/gmane.comp.version-control.git/177857
>> Cc-ing Ákos so he can actually get your message this time. :) (FWIW
>> the convention on this list is always to reply-to-all.)
> Yes, I know, but I replied with the gmane.org site form, and it did not
> CC-ed
next prev parent reply other threads:[~2011-09-05 12:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-02 12:06 Special characters in file name Tajti Ákos
2011-09-02 12:38 ` Alexey Shumkin
2011-09-03 14:46 ` Jonathan Nieder
2011-09-03 20:09 ` Alexey Shumkin
2011-09-05 12:14 ` Tajti Ákos [this message]
[not found] ` <20110905170237.3ed59c6a@ashu.dyn.rarus.ru>
2011-09-05 13:12 ` Tajti Ákos
2011-09-05 13:16 ` Johannes Sixt
2011-09-05 13:33 ` Tajti Ákos
2011-09-03 19:57 ` Jakub Narebski
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=4E64BD3D.6060900@intland.com \
--to=akos.tajti@intland.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
--cc=zapped@mail.ru \
/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).