git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Max Kirillov <max@max630.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Aug 2015, #06; Mon, 31)
Date: Sun, 6 Sep 2015 15:15:37 +0300	[thread overview]
Message-ID: <20150906121537.GA5073@wheezy.local> (raw)
In-Reply-To: <xmqqfv2zt576.fsf@gitster.mtv.corp.google.com>

Hi.

On Mon, Aug 31, 2015 at 04:21:17PM -0700, Junio C Hamano wrote:
> * mk/utf8-no-iconv-warn (2015-06-08) 1 commit
>  - utf8.c: print warning about disabled iconv
> 
>  Warn when a reencoding is requested in a build without iconv
>  support, as the end user is likely to get an unexpected result.  I
>  think the same level of safety should be added to a build with
>  iconv support when the specified encoding is not available, but the
>  patch does not go there.
> 
>  Waiting for a reroll.

I think this can be dropped, I decided to use iconv anyway
so it's not needed for me anymore, and with the requested
additions it's getting too complicated.

-- 
Max

      reply	other threads:[~2015-09-06 12:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-31 23:21 What's cooking in git.git (Aug 2015, #06; Mon, 31) Junio C Hamano
2015-09-06 12:15 ` Max Kirillov [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=20150906121537.GA5073@wheezy.local \
    --to=max@max630.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).