git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Braun <thomas.braun@virtuell-zuhause.de>
To: Konstantin Khomoutov <flatworm@users.sourceforge.net>,
	 Johannes Schindelin <johannes.schindelin@gmx.de>
Cc: "Stefan Näwe" <stefan.naewe@atlas-elektronik.com>,
	"Git Mailing List" <git@vger.kernel.org>,
	msysgit@googlegroups.com, git-for-windows@googlegroups.com
Subject: Re: 4th release candidate of Git for Windows 2.x, was Re: 3rd release candidate of Git for Windows 2.x
Date: Tue, 30 Jun 2015 20:57:59 +0200	[thread overview]
Message-ID: <5592E6B7.10201@virtuell-zuhause.de> (raw)
In-Reply-To: <20150630201523.3a00a2afe9321fb28a6fc82d@domain007.com>

Am 30.06.2015 um 19:15 schrieb Konstantin Khomoutov:
> On Mon, 29 Jun 2015 18:19:09 +0200
> Johannes Schindelin <johannes.schindelin@gmx.de> wrote:
> 
>>> I've finally took time to switch from my old "msys1" release to this
>>> RC4, and immediately got hit by the fact Git is now speaking to me
>>> in Russian, which is not what I want (previously this behaviour was
>>> only exhibited by `git gui` and `gitk`).
>>>
>>> Should I make Git see LC_MESSAGES=en (or other thing like LANG) in
>>> the environment or is there some Git-local method to affect this
>>> behaviour? I tried to grep the release notes using relevant
>>> keywords but was left empty-handed.
>>
>> Personally, I would use LC_ALL=C. Maybe that's good for you, too?
> 
> After reading [1], I've ended up installing LANG=C into my user's
> environment variables -- so far so good, thanks for the tip!

Just for the record.
I created the file lang.sh with contents
export LC_ALL=C
in
/etc/profile.d
which also fixes the problem. And also survives new versions of git.

-- 
-- 
*** Please reply-to-all at all times ***
*** (do not pretend to know who is subscribed and who is not) ***
*** Please avoid top-posting. ***
The msysGit Wiki is here: https://github.com/msysgit/msysgit/wiki - Github accounts are free.

You received this message because you are subscribed to the Google
Groups "msysGit" group.
To post to this group, send email to msysgit@googlegroups.com
To unsubscribe from this group, send email to
msysgit+unsubscribe@googlegroups.com
For more options, and view previous threads, visit this group at
http://groups.google.com/group/msysgit?hl=en_US?hl=en

--- 
You received this message because you are subscribed to the Google Groups "Git for Windows" group.
To unsubscribe from this group and stop receiving emails from it, send an email to msysgit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

  reply	other threads:[~2015-06-30 18:58 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-27 22:11 Release candidate of Git for Windows 2.x is out Johannes Schindelin
2015-05-28 16:25 ` Robert Dailey
2015-06-09  8:43 ` Qb
2015-06-09 12:04   ` Johannes Schindelin
2015-06-09 12:10     ` QbProg
2015-06-09 13:07       ` Johannes Schindelin
2015-06-12 16:30 ` Robert Dailey
2015-06-20 14:16 ` 3rd release candidate of Git for Windows 2.x, was " Johannes Schindelin
2015-06-20 14:59   ` Jon
2015-06-20 15:21     ` Johannes Schindelin
2015-06-20 15:50       ` Robert Dailey
2015-06-29  8:30   ` 4th release candidate of Git for Windows 2.x, was Re: 3rd release candidate of Git for Windows 2.x Johannes Schindelin
2015-06-29  9:07     ` Stefan Näwe
2015-06-29 14:37       ` Johannes Schindelin
2015-06-29 14:49         ` Stefan Näwe
2015-06-29 15:54         ` Konstantin Khomoutov
2015-06-29 16:19           ` Johannes Schindelin
2015-06-30 17:15             ` Konstantin Khomoutov
2015-06-30 18:57               ` Thomas Braun [this message]
2015-07-18 18:48     ` 5th release candidate of Git for Windows 2.x, was Re: 4th " Johannes Schindelin
2015-06-26 11:06 ` Release candidate of Git for Windows 2.x is out Ties
2015-06-27  8:41   ` Johannes Schindelin

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=5592E6B7.10201@virtuell-zuhause.de \
    --to=thomas.braun@virtuell-zuhause.de \
    --cc=flatworm@users.sourceforge.net \
    --cc=git-for-windows@googlegroups.com \
    --cc=git@vger.kernel.org \
    --cc=johannes.schindelin@gmx.de \
    --cc=msysgit@googlegroups.com \
    --cc=stefan.naewe@atlas-elektronik.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).