All of lore.kernel.org
 help / color / mirror / Atom feed
From: ксовиран <xowirun@yandex.ru>
To: Konstantin Khomoutov <kostix+git@007spb.ru>
Cc: git@vger.kernel.org
Subject: Re: git and cyrillic branches
Date: Thu, 25 Jul 2013 18:51:57 +0400	[thread overview]
Message-ID: <322491374763917@web5g.yandex.ru> (raw)
In-Reply-To: <20130725182851.c17d3ed662434d1d91838949@domain007.com>

25.07.2013, 18:28, "Konstantin Khomoutov" <kostix+git@007spb.ru>:
> On Thu, 25 Jul 2013 17:06:41 +0400
> ксовиран <xowirun@yandex.ru> 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
there is nothing wrong with having branches with non-ASCII names as english is not the only language in the world.
problem is still here, i've got ubuntu on VM and same shared git-folder causes this problem on Mac Os and no problems on Ubuntu.
git version on Mac is 1.8.0.1 (on Ubuntu is 1.7.10.4)

  reply	other threads:[~2013-07-25 15:00 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-25 12:19 git and cyrillic branches иванов иван
2013-07-25 12:45 ` Konstantin Khomoutov
     [not found]   ` <992731374757601@web29h.yandex.ru>
2013-07-25 14:28     ` Konstantin Khomoutov
2013-07-25 14:51       ` ксовиран [this message]
2013-07-25 15:26         ` Martin Langhoff
2013-07-25 15:34         ` Konstantin Khomoutov
2013-07-25 16:07         ` Konstantin Khomoutov
2013-07-26  1:50 ` Torsten Bögershausen
2013-07-26  7:35   ` ксовиран

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=322491374763917@web5g.yandex.ru \
    --to=xowirun@yandex.ru \
    --cc=git@vger.kernel.org \
    --cc=kostix+git@007spb.ru \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.