On Thu, 25 Jul 2013 17:06:41 +0400 ксовиран <xowirun@xxxxxxxxx> wrote: > >> hello! there is problem vith git and cyrillic (utf-8) names of > >> branches. branch creates perfectly, but when i clone this remote > >> branch to local host, there are 2 bugs: > >> 1) "git branch" doesnt show checked branch with asterisk (while on > >> remote server it does) > >> 2) "git push" gives 2 errors: "fatal: BRANCH_NAME cannot be > >> resolved to branch." and "fatal: The remote end hung up > >> unexpectedly" thanks. > > > > Works for me across two Debian systems: both have Git 1.7.10.4; user > > accounts on both systems have LANG=en_US.UTF-8 configured in their > > environment. > > > > Do both of your systems (local and remote) have an UTF-8-enabled (or > > encoding-agnostic, like "C") locale active? > > oh, yes indeed. i was pushing from mac to ubuntu, but ubuntu to > ubuntu works fine. although #locale gives almost identical output, so > it is something to work out. спасибо за помощь! 25.07.2013, 16:45, I'm afraid, this might be not that simple: Git received certain tweaks to work around certain problems Mac OS X has (as I understand it) with handling UTF-8 on various filesystems it supports; in particular, see commits 76759c7dff53e8c84e975b88cb8245587c14c7ba [1] and b856ad623e4f686815986c0b9341dd1bfd791e71 [2] which were released as part of v1.7.12. So... I'm not sure, but I beleive these fixes might have been related to handling filenames in the work tree and the index only, not branches, as having branches with non-ASCII names is a weird idea to most developers, I think. So the question is: do you have Git >= 1.7.12 on your Mac OS X machine? If so, do you still experience this problem (I think that Macs do not have non-UTF-8 locales anyway, so this is unlikely the root cause). P.S. Please don't top-post as this breaks discussion flow and hence sucks. 1. https://github.com/git/git/commit/76759c7 2. https://github.com/git/git/commit/b856ad6 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html