Hi Karsten,
Thanks, you helped me a lot. I see now, that logoutputencoding
is for commit header data, not for whole log output. The name
is little missleading, so do description:
i18n.logOutputEncoding
Encoding to use when displaying logs.
Regarding git-log / git-diff output, there are basica
Hi Janusz,
It seems you're mixing up a few completely unrelated concepts here.
Core.quotepath enables quoting and escaping of special characters in file
names. This has nothing to do with character set encoding of file names
(i.e. Cp1250/ISO-8859-2/UTF-8). AFAIK, apart from git-svn, git current
red then.
Janusz Białobrzewski.
Wiadomość Oryginalna
Od: Junio C Hamano
Do: Janusz Białobrzewski
Kopia do: msys...@googlegroups.com, git@vger.kernel.org
Data: 5 sierpnia 2012 21:48
Temat: Re: File path not escaped in warning message
> Janusz Białobrzewski writes:
>
> &
Janusz Białobrzewski writes:
> Here is output from linux:
>
> [janusz@mikrus JavaCommon]$ git config --add core.quotepath false
> [janusz@mikrus JavaCommon]$ git diff --unified=3 -- "1ą.txt"
> warning: LF will be replaced by CRLF in 1.txt.
> The file will have its original line endings in your w
Here is output from linux:
[janusz@mikrus JavaCommon]$ git config --add core.quotepath false
[janusz@mikrus JavaCommon]$ git diff --unified=3 -- "1ą.txt"
warning: LF will be replaced by CRLF in 1.txt.
The file will have its original line endings in your working directory.
diff --git a/1.txt b/1.
Janusz Białobrzewski writes:
> I have enabled core.quotepath, but file path in warning isn't escaped:
> File name is 1ą.txt its content is encoded in windows-1250
> Output of git diff after reencoding to windows1250 is:
>
> warning: LF will be replaced by CRLF in 1Ä….txt.
> The file will have its
6 matches
Mail list logo
