From: Aurelien Jarno <aurelien@aurel32.net>
To: Stefan Weil <weil@mail.berlios.de>
Cc: Anthony Liguori <aliguori@us.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Next stable release
Date: Tue, 07 Apr 2009 12:03:50 +0200 [thread overview]
Message-ID: <49DB2506.9080101@aurel32.net> (raw)
In-Reply-To: <49DB1C8E.2000605@mail.berlios.de>
Stefan Weil a écrit :
> Aurelien Jarno schrieb:
>> Stefan Weil a écrit :
>>
>>> Anthony Liguori schrieb:
>>>
>>>> Stefan Weil wrote:
>>>>
>>>>> Anthony Liguori schrieb:
>>>>>
>>>>>
>>>>>> I'd like to cut 0.10.2 on Monday at around 5PM CST.
>>>>>>
>>>>>> If there are patches outstanding, now's a good time to mention it.
>>>>>>
>>>>>>
>>>>>>
>>>>> Maybe this one (fixes documentation):
>>>>>
>>>>> http://lists.gnu.org/archive/html/qemu-devel/2009-03/msg01609.html
>>>>>
>>>>> Stable branches should not contain broken links...
>>>>>
>>>>>
>>>> I think ohw has already been removed, no?
>>>>
>>>> Regards,
>>>>
>>>> Anthony Liguori
>>>>
>>>>
>>> I just had a look - yes, you are right.
>>> ppc_rom.bin has been removed somewhere in the past.
>>>
>> Wrong, ppc_rom.bin is still there and still in use by ppc_prep.c
>>
>>
>>> Then ohw should also be removed from qemu-doc.texi and pc-bios/README.
>>> I updated my patch to do this.
>>>
>> Therefore this patch is also wrong.
>>
>>
>
>
> Oh, I need a better monitor! Thank you, Aurelien, for correcting me.
>
> But why do you write "also wrong"?
Because your new patch is wrong. The old patch is not
> I think my first patch was the better one, ohw was not removed!
>
> So the first patch should be applied to stable and trunk
> because ohw has no longer a valid URL and is no longer supported
> (pbrook said so on #qemu-devel) even if it is still included.
Agreed.
--
Aurelien Jarno GPG: 1024D/F1BCDB73
aurelien@aurel32.net http://www.aurel32.net
next prev parent reply other threads:[~2009-04-07 10:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-05 19:38 [Qemu-devel] Next stable release Anthony Liguori
2009-04-06 13:08 ` TeLeMan
2009-04-06 13:43 ` Anthony Liguori
2009-04-07 1:38 ` Edgar E. Iglesias
2009-04-06 21:03 ` malc
2009-04-10 2:35 ` TeLeMan
2009-04-10 2:54 ` malc
2009-04-10 3:04 ` TeLeMan
2009-04-10 4:17 ` malc
2009-04-06 14:51 ` Stefan Weil
2009-04-07 1:11 ` Anthony Liguori
2009-04-07 6:06 ` Stefan Weil
2009-04-07 7:16 ` Aurelien Jarno
2009-04-07 9:27 ` Stefan Weil
2009-04-07 10:03 ` Aurelien Jarno [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-03-20 16:23 Anthony Liguori
2009-03-20 17:02 ` René Rebe
2009-03-20 20:20 ` Robert Riebisch
2009-03-21 9:05 ` 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=49DB2506.9080101@aurel32.net \
--to=aurelien@aurel32.net \
--cc=aliguori@us.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=weil@mail.berlios.de \
/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).