Re: Weird filename encoding issue

On Fri, Oct 17, 2008 at 11:59 AM, Alexander Gladysh <agladysh@gmail.com> wrote:

My apologies, Gmail eaten part of my message.

Sorry for such old Git versions, I can not upgrade right now. Perhaps it was fixed in 1.6.x?

Steps to reproduce:

1. Create git repo on Windows machine, add there file, named
"Копия.txt" (Russian for Copy.txt) in CP1251 (NOT UTF-8). Just in
case, hopefully correctly named file is attached.

File must be added and committed from git gui, not from command line.

$ mkdir test && cd test $ git init <put file there> $ git gui

2. Share the repo somewhere, so it would be accessible from OS X (repo
should still be on Windows machine).

3. Clone repo to OS X machine and see the weird behaviour. Git status
can't decide how file should be named, "%CA%EE%EF%E8%FF.txt" or
"\312\356\357\350\377.txt".

$ git clone /Volumes/Exchange/test/ Initialized empty Git repository in /Users/agladysh/test/.git/ $ cd test $ git status # On branch master # Untracked files: # (use "git add <file>..." to include in what will be committed) # # %CA%EE%EF%E8%FF.txt nothing added to commit but untracked files present (use "git add" to track) $ ls %CA%EE%EF%E8%FF.txt $ git clean -fd Removing %CA%EE%EF%E8%FF.txt $ git status # On branch master # Changed but not updated: # (use "git add/rm <file>..." to update what will be committed) # # deleted: "\312\356\357\350\377.txt" # no changes added to commit (use "git add" and/or "git commit -a")

Alexander.