S
S
sadgb2012-02-02 15:46:20
git
sadgb, 2012-02-02 15:46:20

Git windows+linux Russian filename problem

The meaning is this
Let's say 2 developers
1 on Windows
2 on Ubuntu

Now the first developer adds a file with a Russian name to the git (that's a bastard) and pushes
Now the second one makes a pool on Ubuntu and gets the file name %EA%EE%EC%EC%E5 %ED%F2%E0%F0%E8%FF%EC%E8
and this is not the worst - git status says that a new file with the corresponding name has appeared
and cannot be changed - it simply does not find it
And so on all unixes and

Macs Server Gitolight How

can I fix this?
Where is the same setting so that the server has normal file names?
If not, is there an easy way to disable non-english characters in commit names?

Answer the question

In order to leave comments, you need to log in

5 answer(s)
Z
Zloy1, 2012-02-02
@Zloy1

… is there an easy way to disable non-english characters in commit names?
there is an easy way - to use the git pre-receive hook in the remote rep where the push is given, and you can also use the git pre-commit hook in the developers' local reps.
read about hooks here , there are also examples of such hooks

A
Anatoly, 2012-02-02
@taliban

I don’t know how to git, but on svn you can attach a pre-check before the commit =) and check <substitute what you need here>. In your case, the best check is /[\w\-]+/. No need to fight the wind, ban such files, or give lyuley to the one who commits such files. This seems to me the best option.

B
Beholder, 2012-02-02
@Beholder

From msysgit ReleaseNotes.rtf:
git and bash have serious problems with non-ASCII file names (Issue 80, 159).

S
sadgb, 2012-02-02
@sadgb

Yes, you will have to limit the names of the files when pushing

V
vikignt, 2012-02-02
@vikignt

On Windows, install msysgit-unicode with unicode support, and then push

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question