9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: lucio@proxima.alt.za
To: 9fans@cse.psu.edu
Subject: [9fans] Re: [Xen-devel] [PATCH] XML-RPC: Cope with large integers on x86-64
Date: Tue, 28 Mar 2006 07:12:00 +0200	[thread overview]
Message-ID: <da068fc16e59978651cc48bca463426d@proxima.alt.za> (raw)
In-Reply-To: <44289F79.9000501@us.ibm.com>

> I see this as a temporary solution until
> we can sanitize the XML-RPC functions and get rid of all the
> S-Expression stuff.

Now, was that what drove Ron away from Xen?

I find it hard to follow the mailing list and especially the breakneck
speed with which they seem to be advancing.  I can only presume it is
modelled on Linux development, it certainly seems to clash violently
with the NetBSD and Plan 9 cultures of caution and backwards
compatibility.

No principle of least surprise in their department :-)

++L



           reply	other threads:[~2006-03-28  5:12 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <44289F79.9000501@us.ibm.com>]

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=da068fc16e59978651cc48bca463426d@proxima.alt.za \
    --to=lucio@proxima.alt.za \
    --cc=9fans@cse.psu.edu \
    /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).