All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alvin Starr <alvin@iplink.net>
To: xen-devel@lists.sourceforge.net
Subject: X86_64 status?
Date: Fri, 18 Feb 2005 10:44:01 -0500	[thread overview]
Message-ID: <42160D41.7070902@Iplink.net> (raw)
In-Reply-To: <Pine.LNX.4.58.0502180815070.21698@enigma.lanl.gov>


What is the current state of the x86_64 port?

On another note. I am sure it is a silly question but is anybody wacking 
away on an Alpha port?

-- 
Alvin Starr                   ||   voice: (416)585-9971
Interlink Connectivity        ||   fax:   (416)585-9974
alvin@iplink.net              ||




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

  reply	other threads:[~2005-02-18 15:44 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-18 13:26 autotoolizing xen? Tobias Hunger
2005-02-18 15:15 ` Ronald G. Minnich
2005-02-18 15:44   ` Alvin Starr [this message]
2005-02-18 15:53   ` Tobias Hunger
2005-02-18 16:06     ` Christian Limpach
2005-02-18 16:33       ` Nivedita Singhvi
2005-02-18 16:03   ` Anthony Liguori
2005-02-18 16:30     ` Tobias Hunger
2005-02-18 19:20   ` Jacob Gorm Hansen
2005-02-18 20:04     ` Anthony Liguori
2005-02-18 20:03       ` Jacob Gorm Hansen
2005-03-07 10:01         ` Nick Craig-Wood
2005-02-18 21:25     ` Tobias Hunger
2005-02-18 19:56   ` Adam Sulmicki
2005-02-19 13:10 ` Keir Fraser
  -- strict thread matches above, loose matches on Subject: below --
2005-02-20 10:58 X86_64 status? Ian Pratt

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=42160D41.7070902@Iplink.net \
    --to=alvin@iplink.net \
    --cc=xen-devel@lists.sourceforge.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.