From: BALATON Zoltan <balaton@eik.bme.hu>
To: Nicholas Piggin <npiggin@gmail.com>
Cc: Bernhard Beschow <shentey@gmail.com>,
qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
Daniel Henrique Barboza <danielhb413@gmail.com>,
clg@kaod.org
Subject: Re: [PATCH v3] docs/system/ppc: Document running Linux on AmigaNG machines
Date: Tue, 12 Mar 2024 16:50:07 +0100 (CET) [thread overview]
Message-ID: <alpine.LMD.2.03.2403121645090.11217@eik.bme.hu> (raw)
In-Reply-To: <CZRUH5CRDRDU.3NS44E5KB0SSY@wheely>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1711 bytes --]
On Wed, 13 Mar 2024, Nicholas Piggin wrote:
> On Tue Mar 12, 2024 at 8:36 PM AEST, Nicholas Piggin wrote:
>> On Tue Mar 12, 2024 at 7:28 PM AEST, Bernhard Beschow wrote:
>>>
>>>
>>> Am 9. März 2024 11:34:56 UTC schrieb BALATON Zoltan <balaton@eik.bme.hu>:
>>>> On Thu, 29 Feb 2024, BALATON Zoltan wrote:
>>>>> On Wed, 21 Feb 2024, BALATON Zoltan wrote:
>>>>>> Documentation on how to run Linux on the amigaone, pegasos2 and
>>>>>> sam460ex machines is currently buried in the depths of the qemu-devel
>>>>>> mailing list and in the source code. Let's collect the information in
>>>>>> the QEMU handbook for a one stop solution.
>>>>>
>>>>> Ping? (Just so it's not missed from next pull.)
>>>>
>>>> Ping for freeze.
>>>
>>> Has this patch been tagged yet? It would really be a pity if it didn't make it into 9.0.
>>
>> Will send out a PR today and I'll include it.
>>
>>>
>>> FWIW:
>>>
>>> Reviewed-by: Bernhard Beschow <shentey@gmail.com>
>>
>> Thanks, always helpful.
>
> Oh you are Co-author. Sorry, took some time for light bulb
> to turn on... In that case it needs your SOB to merge.
>
> I will have to leave it out of the PR if I don't get that in
> time, but we should be able to get a doc improvement past
> the soft freeze. It's essentially a usability bug-fix.
This was the original submission that compiled my previous emails and
cover letters into some docs so the text was mine and editorship was
Bernhard:
https://patchew.org/QEMU/20231216123013.67978-1-shentey@gmail.com/
which I then took over and enhanced further so you can take his SoB from
that patch I just forgot to retain it as I did not think it would be
needed.
Regards,
BALATON Zoltan
next prev parent reply other threads:[~2024-03-12 15:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 23:22 [PATCH v3] docs/system/ppc: Document running Linux on AmigaNG machines BALATON Zoltan
2024-02-29 11:58 ` BALATON Zoltan
2024-03-09 11:34 ` BALATON Zoltan
2024-03-12 9:28 ` Bernhard Beschow
2024-03-12 10:36 ` Nicholas Piggin
2024-03-12 14:34 ` Nicholas Piggin
2024-03-12 15:50 ` BALATON Zoltan [this message]
2024-03-12 23:21 ` Bernhard Beschow
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=alpine.LMD.2.03.2403121645090.11217@eik.bme.hu \
--to=balaton@eik.bme.hu \
--cc=clg@kaod.org \
--cc=danielhb413@gmail.com \
--cc=npiggin@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=shentey@gmail.com \
/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).