From: Jeff King <peff@peff.net>
To: Brandon Casey <casey@nrlssc.navy.mil>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH 2/2] t8005: convert CP1251 character set to ISO8859-5
Date: Thu, 28 May 2009 14:47:58 -0400 [thread overview]
Message-ID: <20090528184758.GC13499@coredump.intra.peff.net> (raw)
In-Reply-To: <xZbeuW5cnER48WqsONW1BxZmepHjuwJtRUnpLAV0nv4mheMkGHT26g@cipher.nrlssc.navy.mil>
On Tue, May 26, 2009 at 09:57:41AM -0500, Brandon Casey wrote:
> > With current 'next' and NO_PERL set, I can pass every test except:
>
> Oh, and have the recent changes that are now in next _allowed_ any new
> tests to pass that were previously failing?
Just one. It had been a while since I re-checked the skipped tests, so
most of what I found I could now pass was unrelated. But I believe your
recent patches fixed t3901 for me. On current 'next', it passes, but on
current 'maint', it says something like "cannot convert UTF-8 to utf-8".
-Peff
next prev parent reply other threads:[~2009-05-28 18:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-22 15:25 [PATCH] t8005: use more portable character encoding names Brandon Casey
2009-05-22 16:22 ` Junio C Hamano
2009-05-22 16:51 ` Brandon Casey
2009-05-22 23:04 ` Alex Riesen
2009-05-22 23:47 ` [PATCH 1/2] " Brandon Casey
2009-05-22 23:47 ` [PATCH 2/2] t8005: convert CP1251 character set to ISO8859-5 Brandon Casey
2009-05-23 1:02 ` Junio C Hamano
2009-05-23 1:06 ` Junio C Hamano
2009-05-25 9:20 ` Jeff King
2009-05-25 9:26 ` Jeff King
2009-05-26 14:56 ` Brandon Casey
2009-05-28 18:43 ` Jeff King
2009-05-26 14:57 ` Brandon Casey
2009-05-28 18:47 ` Jeff King [this message]
2009-05-26 22:56 ` Junio C Hamano
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=20090528184758.GC13499@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=casey@nrlssc.navy.mil \
--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).