From: Jonathan Nieder <jrnieder@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Brian Gernhardt <brian@gernhardtsoftware.com>,
Git List <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] Ensure __BYTE_ORDER is always set
Date: Thu, 30 Jan 2014 14:12:05 -0800 [thread overview]
Message-ID: <20140130221205.GI27577@google.com> (raw)
In-Reply-To: <20140130204538.GA1130@sigill.intra.peff.net>
Hi,
Jeff King wrote:
> I do find the failure mode interesting. The endian-swapping code kicked
> in when it did not
Odd --- wouldn't the #if condition expand to '0 != 0'?
next prev parent reply other threads:[~2014-01-30 22:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 19:55 [PATCH] Ensure __BYTE_ORDER is always set Brian Gernhardt
2014-01-30 20:45 ` Jeff King
2014-01-30 21:50 ` Jeff King
2014-01-31 2:35 ` Eric Sunshine
2014-01-30 22:12 ` Jonathan Nieder [this message]
2014-01-30 22:48 ` Jeff King
2014-01-30 23:24 ` Brian Gernhardt
2014-01-30 22:02 ` Jonathan Nieder
2014-01-30 22:46 ` Jeff King
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=20140130221205.GI27577@google.com \
--to=jrnieder@gmail.com \
--cc=brian@gernhardtsoftware.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
/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).