Re: [PATCH 05/15] sequencer: use logmsg_reencode in get_message
- From
Jeff King <peff@peff.net>
- Date
- Jun 10, 2014, 21:50 UTC
- Message-ID
- <20140610215022.GC19107@sigill.intra.peff.net>
- In-Reply-To
- <xmqq7g4o8mup.fsf@gitster.dls.corp.google.com>
On Tue, Jun 10, 2014 at 02:40:30PM -0700, Junio C Hamano wrote:
Show 19 quoted lines
> Jeff King <peff@peff.net> writes: > > > Note that we may be fixing a bug here. The existing code > > does: > > > > if (same_encoding(to, from)) > > reencode_string(buf, to, from); > > > > That probably should have been "!same_encoding". > > > > Signed-off-by: Jeff King <peff@peff.net> > > --- > > I didn't actually test for the bug, so it's possible that I'm missing > > something clever... > > Thanks for spotting. There is nothing clever going on. > > 0e18bcd5 (reencode_string(): introduce and use same_encoding(), > 2012-10-18) has this misconversion.
Ah, thanks, I tried digging but didn't see anything obvious (and somehow my eyes glossed over the s/same_encoding/strcmp/ while reading the history). I feel much better about the change now.
-Peff