Re: [PATCH v2] utf8: handle systems that don't write BOM for UTF-16

From: brian m. carlson <sandals@crustytoothpaste.net>
Date: Feb 11, 2019, 01:20 UTC
Message-ID: <20190211012047.GA684736@genre.crustytoothpaste.net>
In-Reply-To: <CAPig+cRTRCeGZ115gJGGNPtQ7WyFWg4Y45WOPec-8CmnG6ZRMQ@mail.gmail.com>

On Sun, Feb 10, 2019 at 08:16:26PM -0500, Eric Sunshine wrote:

Show 11 quoted lines

> On Sun, Feb 10, 2019 at 7:23 PM brian m. carlson
> <sandals@crustytoothpaste.net> wrote:
> > When serializing UTF-16 (and UTF-32), there are three possible ways to
> > write the stream. One can write the data with a BOM in either big-endian
> > or little-endian format, or one can write the data without a BOM in
> > big-endian format.
> > [...]
> > Signed-off-by: brian m. carlson <sandals@crustytoothpaste.net>
> 
> Premature git-send-email invocation? The commit message of v2 seems to
> be a bit different from v1, but the patch itself is identical.

Oof, I forgot to run "git add -u" before running "git commit --amend". Thanks for catching this; I'll send out a v3 in a second.

-- 
brian m. carlson: Houston, Texas, US
OpenPGP: https://keybase.io/bk2204