git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Duy Nguyen <pclouds@gmail.com>
Cc: "Trần Ngọc Quân" <vnwildman@gmail.com>,
	git-malling-list <git@vger.kernel.org>,
	698867@bugs.debian.org
Subject: Re: gettext CTYPE for libc
Date: Mon, 25 Nov 2013 11:31:02 -0800	[thread overview]
Message-ID: <20131125193102.GM4212@google.com> (raw)
In-Reply-To: <CACsJy8CMUMdzJyDABFj47oY8j8kKr5K88niXoM0o4dVQkWvkqA@mail.gmail.com>

Duy Nguyen wrote:

>             Do you think it's ok to revert the workaround if we detect
> the running glibc is fixed (or if it does not run glibc at all)? I
> think we could use gnu_get_libc_version() to detect it.

That would be wonderful.

Thanks,
Jonathan

      reply	other threads:[~2013-11-25 19:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-23  2:15 gettext CTYPE for libc Trần Ngọc Quân
2013-11-24  9:05 ` Thomas Rast
2013-11-25  1:32   ` Trần Ngọc Quân
2013-11-25  7:20 ` Duy Nguyen
2013-11-25 19:31   ` Jonathan Nieder [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=20131125193102.GM4212@google.com \
    --to=jrnieder@gmail.com \
    --cc=698867@bugs.debian.org \
    --cc=git@vger.kernel.org \
    --cc=pclouds@gmail.com \
    --cc=vnwildman@gmail.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).