From: Teemu Likonen <tlikonen@iki.fi>
To: Gregory Petrosyan <gregory.petrosyan@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: non-ascii filenames issue
Date: Sun, 05 Apr 2009 12:54:28 +0300 [thread overview]
Message-ID: <87ab6v2zor.fsf@iki.fi> (raw)
In-Reply-To: <20090405093640.GA9803@home> (Gregory Petrosyan's message of "Sun\, 5 Apr 2009 13\:36\:40 +0400")
On 2009-04-05 13:36 (+0400), Gregory Petrosyan wrote:
> # Changes to be committed:
> # (use "git rm --cached <file>..." to unstage)
> #
> # new file: "\321\204\320\260\320\271\320\273"
> #
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> "файл" should be here instead
It can be fixed with command:
git config --global core.quotepath false
next prev parent reply other threads:[~2009-04-05 9:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-05 9:36 non-ascii filenames issue Gregory Petrosyan
2009-04-05 9:54 ` Teemu Likonen [this message]
2009-04-05 10:01 ` Gregory Petrosyan
2009-04-05 10:51 ` John Tapsell
2009-04-05 16:23 ` Jay Soffian
2009-04-05 19:29 ` Junio C Hamano
2009-04-05 20:22 ` Jay Soffian
2009-04-06 7:28 ` Peter Krefting
2009-04-06 9:12 ` Johannes Schindelin
2009-04-06 22:33 ` Dmitry Potapov
2009-04-07 8:26 ` demerphq
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=87ab6v2zor.fsf@iki.fi \
--to=tlikonen@iki.fi \
--cc=git@vger.kernel.org \
--cc=gregory.petrosyan@gmail.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).