public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Teemu Likonen <tlikonen@iki•fi>
To: "Antonio García Domínguez" <nyoescape@gmail•com>
Cc: git@vger•kernel.org
Subject: Re: "add -p" + filenames with UTF-8 multibyte characters = "No  changes"
Date: Sun, 15 Feb 2009 21:11:00 +0200	[thread overview]
Message-ID: <87prhjqzwb.fsf@iki.fi> (raw)
In-Reply-To: <2b8265360902151100n2eca0182odf9543c1dd8a7f98@mail.gmail.com> ("Antonio García Domínguez"'s message of "Sun\, 15 Feb 2009 20\:00\:38 +0100")

[Added the Git list back to delivery.]

On 2009-02-15 20:00 (+0100), Antonio García Domínguez wrote:

>> This bug is documented in BUGS section of "git add" manual (see "git
>> help add"). You can work it around with
>>
>>    git config --global core.quotepath false
>
> Oh, sorry, I should have known better and RTFM. :-D

No problem at all. I was bitten by the same bug earlier, and as I wasn't
able to fix it I sent a documentation patch instead. :-)

"core.quotepath=false" is good for other purposes too. It prints UTF-8
filenames in diff headers in form that is actually readable. I think it
would be better default.

  parent reply	other threads:[~2009-02-15 19:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-15 18:40 "add -p" + filenames with UTF-8 multibyte characters = "No changes" Antonio García Domínguez
2009-02-15 18:59 ` Teemu Likonen
     [not found]   ` <2b8265360902151100n2eca0182odf9543c1dd8a7f98@mail.gmail.com>
2009-02-15 19:11     ` Teemu Likonen [this message]
2009-02-16  3:36       ` Jeff King
2009-02-16  4:00         ` Junio C Hamano
2009-02-17  7:02           ` [PATCH] git-add -i/-p: learn to unwrap C-quoted paths Junio C Hamano
2009-02-17  8:09             ` Teemu Likonen
2009-02-16  5:13         ` "add -p" + filenames with UTF-8 multibyte characters = "No changes" Teemu Likonen

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=87prhjqzwb.fsf@iki.fi \
    --to=tlikonen@iki$(echo .)fi \
    --cc=git@vger$(echo .)kernel.org \
    --cc=nyoescape@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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