All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Weil <weil@mail.berlios.de>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
	Aurelien Jarno <aurelien@aurel32.net>,
	Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [PATCH] doc: Remove old URL for Open Hack'Ware.
Date: Sat, 06 Jun 2009 17:50:31 +0200	[thread overview]
Message-ID: <4A2A9047.5020301@mail.berlios.de> (raw)
In-Reply-To: <f43fc5580906060828t570e3dfdgeb2cf011d74cc987@mail.gmail.com>

Blue Swirl schrieb:
> On 6/6/09, Stefan Weil <weil@mail.berlios.de> wrote:
>> The URL http://perso.magic.fr/l_indien/ no longer exists.
>>
>> Signed-off-by: Stefan Weil <weil@mail.berlios.de>
>
> Removing only the references would mean that we'd have mysterious
> binaries without any explanation in pc-bios. We should also delete
> ppc_rom.bin, ohw.diff and support for loading OHW but that would make
> PREP machine untestable.

For insiders, there is nothing mysterious because they know
the history.

For other people, a URL which is invalid does not help,
so the binaries are already mysterious today.
I did not find any valid URL with the sources.

Maybe the QEMU maintainers can add a git submodule
containing the OHW sources from Debian's package
openhackware?

This was the latest contribution to the previous discussion:

http://lists.gnu.org/archive/html/qemu-devel/2009-04/msg00312.html

I came to the conclusion that PREP support is still wanted,
so the binaries should remain part of QEMU.

Stefan

  reply	other threads:[~2009-06-06 15:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-31 16:26 [Qemu-devel] [PATCH] [STABLE] Update documentation for OpenHackWare Stefan Weil
2009-06-06 15:12 ` [Qemu-devel] [PATCH] doc: Remove old URL for Open Hack'Ware Stefan Weil
2009-06-06 15:28   ` Blue Swirl
2009-06-06 15:50     ` Stefan Weil [this message]
2009-06-06 16:09       ` Blue Swirl
2009-06-06 21:15         ` Paul Brook
2009-06-06 21:58       ` Andreas Färber

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=4A2A9047.5020301@mail.berlios.de \
    --to=weil@mail.berlios.de \
    --cc=aurelien@aurel32.net \
    --cc=blauwirbel@gmail.com \
    --cc=paul@codesourcery.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 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.