From: "Alexander Gladysh" <agladysh@gmail.com>
To: msysgit@googlegroups.com, git@vger.kernel.org
Subject: Re: Weird filename encoding issue
Date: Fri, 17 Oct 2008 12:08:04 +0400 [thread overview]
Message-ID: <c6c947f60810170108q3038b66bj2ad89bdcb7105903@mail.gmail.com> (raw)
In-Reply-To: <c6c947f60810170059s3859d906r9935b5e80d8a41c6@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1585 bytes --]
On Fri, Oct 17, 2008 at 11:59 AM, Alexander Gladysh <agladysh@gmail.com> wrote:
> Hi, all!
>
> OS X 10.5.5 (English locale), Git 1.5.5.1
> Windows XP SP2 (Russian), msysGit 1.5.6.1.1071.g76fb
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.
[-- Attachment #2: Copy.zip --]
[-- Type: application/zip, Size: 116 bytes --]
next prev parent reply other threads:[~2008-10-17 8:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-17 7:59 Weird filename encoding issue Alexander Gladysh
2008-10-17 8:08 ` Alexander Gladysh [this message]
2008-10-17 8:55 ` Johannes Sixt
2008-10-18 2:58 ` Robin Rosenberg
2008-10-27 8:08 ` [msysGit] " Peter Krefting
2008-10-18 6:22 ` Alexander Gladysh
2008-10-18 9:35 ` [msysGit] " Robin Rosenberg
2008-10-18 17:51 ` Johannes Sixt
2008-10-19 14:11 ` [msysGit] " Alexander Gladysh
2008-10-17 8: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=c6c947f60810170108q3038b66bj2ad89bdcb7105903@mail.gmail.com \
--to=agladysh@gmail.com \
--cc=git@vger.kernel.org \
--cc=msysgit@googlegroups.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).