From: Jakub Narebski <jnareb@gmail.com>
To: "Alexander Gladysh" <agladysh@gmail.com>
Cc: msysgit@googlegroups.com, git@vger.kernel.org
Subject: Re: Weird filename encoding issue
Date: Fri, 17 Oct 2008 01:57:36 -0700 (PDT) [thread overview]
Message-ID: <m3hc7bk39g.fsf@localhost.localdomain> (raw)
In-Reply-To: <c6c947f60810170108q3038b66bj2ad89bdcb7105903@mail.gmail.com>
"Alexander Gladysh" <agladysh@gmail.com> writes:
> 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".
I _suspect_ that it is caused by known issue with MacOS X filesystem
in default settings. Git assumes that what he puts in filesystem is
the same that it reads from filesystem; there is ongoing (although
bit stalled) effort to make Git work around this. Unfortunately HFS+
does not, I think, fullfil this requirement.
--
Jakub Narebski
Poland
ShadeHawk on #git
prev parent reply other threads:[~2008-10-17 8:58 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
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 [this message]
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=m3hc7bk39g.fsf@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=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).