From: Pete Zaitcev <zaitcev@redhat.com>
To: Jeff Garzik <jeff@garzik.org>
Cc: Project Hail List <hail-devel@vger.kernel.org>
Subject: Re: [hail patch 2/3] fix 32/64 wire interoperability
Date: Thu, 5 Aug 2010 17:19:51 -0600 [thread overview]
Message-ID: <20100805171951.5a4dbb54@lembas.zaitcev.lan> (raw)
In-Reply-To: <4C5B2C4A.8000808@garzik.org>
On Thu, 05 Aug 2010 17:25:30 -0400
Jeff Garzik <jeff@garzik.org> wrote:
> I wonder if we shouldn't switch to attribute(packed) for safety, though.
I dunno, as long as we test this... I irrationally hate the
gcc attributes, although probably any viable competitor will have
to support them. Talk about embrace-and-extend. Fine when FSF does
it, not fine when Microsoft does, huh.
-- Pete
prev parent reply other threads:[~2010-08-05 23:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 23:16 [hail patch 2/3] fix 32/64 wire interoperability Pete Zaitcev
2010-08-05 21:25 ` Jeff Garzik
2010-08-05 23:19 ` Pete Zaitcev [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=20100805171951.5a4dbb54@lembas.zaitcev.lan \
--to=zaitcev@redhat.com \
--cc=hail-devel@vger.kernel.org \
--cc=jeff@garzik.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).