From: Tero Kaarlela <tero.kaarlela@kotinet.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: What happened to linuxppc-img from Freeoszoo
Date: Sat, 25 Jun 2005 22:58:57 +0300 [thread overview]
Message-ID: <42BDB781.4090604@kotinet.com> (raw)
In-Reply-To: <slrndbqv01.tl7.draga@dragas.org>
Stefano Marinelli wrote:
>On Sat, 25 Jun 2005 19:23:01 +0300, Tero Kaarlela wrote:
>
>
>>>I've put a new updated image. It works. It's on the freeoszoo
>>>
>>>
>> Of reactos not linuxppc?
>>
>>
>
>Reactos. If I'll have some time, in the next days, I could prepare a ppc
>sarge image.
>
>
>
It would be nice since I am trying to add things to PREP residual data.
And it would be easier to see everything goes in correctly with a
working linux.
Tero
prev parent reply other threads:[~2005-06-25 17:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-24 21:52 [Qemu-devel] What happened to linuxppc-img from Freeoszoo Tero Kaarlela
2005-06-24 19:21 ` jeebs
2005-06-25 11:19 ` [Qemu-devel] " Stefano Marinelli
2005-06-25 16:23 ` Tero Kaarlela
2005-06-25 15:45 ` Stefano Marinelli
2005-06-25 19:58 ` Tero Kaarlela [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=42BDB781.4090604@kotinet.com \
--to=tero.kaarlela@kotinet.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).