qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: "J.C. Pizarro" <jcpiza@gmail.com>
Subject: Re: [Qemu-devel] What 64-bit CPU targets dominate in the future?
Date: Wed, 8 Aug 2007 15:03:12 +0100	[thread overview]
Message-ID: <200708081503.13753.paul@codesourcery.com> (raw)
In-Reply-To: <998d0e4a0708061736w7166102uc0caa85cf0544f8d@mail.gmail.com>

> What popularity of CPU will dominate in the years 2008 .. 2013?

AFAICS this has nothing to do with qemu.
Please don't post random unrelated questions to this list.

You've already been told the same thing on some of the other lists you posted 
the exact same mail to.

Paul

      reply	other threads:[~2007-08-08 14:03 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <998d0e4a0708061637x4dfe0dew1edda6105e77a833@mail.gmail.com>
2007-08-07  0:36 ` [Qemu-devel] What 64-bit CPU targets dominate in the future? J.C. Pizarro
2007-08-08 14:03   ` Paul Brook [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=200708081503.13753.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=jcpiza@gmail.com \
    --cc=qemu-devel@nongnu.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 NNTP newsgroup(s).