From: Tim Wiess <tim@nop.cx>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] VESA ISO Changes?
Date: Fri, 4 Nov 2005 08:38:36 -0800 [thread overview]
Message-ID: <d138fc5fc98ad44db2717c9f0e6803d5@akira.nop.cx> (raw)
In-Reply-To: <ee9e417a0511030857s749a3dafg678e49bfef5a7cab@mail.gmail.com>
> The vesa code will be included with the new VM changes, which
> should appear within a week or so.
Just out of curiosity, what type of changes are you incorporating?
Are they just machine specific (x86) changes or have you been working
on the mi part of the VM as well?
next prev parent reply other threads:[~2005-11-04 16:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-03 16:28 LiteStar numnums
2005-11-03 16:39 ` Christoph Lohmann
2005-11-03 16:47 ` LiteStar numnums
2005-11-03 16:58 ` Christoph Lohmann
2005-11-03 17:43 ` LiteStar numnums
2005-11-03 16:57 ` Russ Cox
2005-11-03 16:57 ` Christoph Lohmann
2005-11-04 16:38 ` Tim Wiess [this message]
2005-11-03 16:43 ` [9fans] " LiteStar numnums
2005-11-04 2:32 [9fans] " YAMANASHI Takeshi
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=d138fc5fc98ad44db2717c9f0e6803d5@akira.nop.cx \
--to=tim@nop.cx \
--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).