All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Mayer" <l_indien@magic.fr>
To: Thayne Harbaugh <thayne@realmsys.com>
Cc: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Re: PPC fixes for qemu/OpenHackWare
Date: Wed, 09 Feb 2005 00:32:54 +0100	[thread overview]
Message-ID: <1107905574.10555.32.camel@rapid> (raw)
In-Reply-To: <1107901543.14935.48.camel@localhost.localdomain>

On Tue, 2005-02-08 at 23:25, Thayne Harbaugh wrote:
> On Tue, 2005-02-08 at 23:11 +0100, J. Mayer wrote:
> > On Tue, 2005-02-08 at 20:45, Thayne Harbaugh wrote:
> > > These fixes greatly improve qemu booting on PPC - many Linux
> > > distributions with kernel 2.4 now work.  It's two big patches (one for
> > > qemu, one for OpenHackWare) - let me know if someone prefers them broken
> > > out into smaller pieces.
> > > 
> > > There's still some work to be done to get PREP in good shape as well as
> > > a Linux 2.6 kernel to work well - expect some more patches in the near
> > > future.
> > 
> > Hi.
> > Thanks for the work. I need to take a close look of your patches because
> > I completely restructured OHW. For example, HFS code is quite different
> > in my working repository (but still have problems on some fs)...
[...]
> > I can't compare OHW for now, as it seems that most of the patch is
> > cosmetic (blanks, tabs) and as most files have changed. Could you please
> > regenerate the patch using:
> > --ignore-all-space --ignore-blank-lines --ignore-space-change --minimal
> > -p
> > options to make it easier to read ?
> 
> I'm a bit confused.  I closely reviewed the patch prior to sending and I
> didn't notice any instances of whitespace-only diff.  There are,
> however, many lines of spelling changes. :)  controler -> controller,
> recurs -> recurse, to -> too, etc..

Oh well, I looked closer, and you're absolutely right, there are lots of
typo I didn't saw at first sight.... I'm sorry about my mistake.
But I would still appreciate a diff with -p option, then I have the
function name with the diff, which may helps when code has been
splitted...

-- 
J. Mayer <l_indien@magic.fr>
Never organized

  reply	other threads:[~2005-02-08 23:49 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-08 19:45 [Qemu-devel] PPC fixes for qemu/OpenHackWare Thayne Harbaugh
2005-02-08 20:46 ` Fabrice Bellard
2005-02-08 21:06   ` Thayne Harbaugh
2005-02-08 22:12     ` Hetz Ben Hamo
2005-02-08 22:11 ` [Qemu-devel] " J. Mayer
2005-02-08 22:25   ` Thayne Harbaugh
2005-02-08 23:32     ` J. Mayer [this message]
2005-02-09 18:50 ` [Qemu-devel] " Thayne Harbaugh

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=1107905574.10555.32.camel@rapid \
    --to=l_indien@magic.fr \
    --cc=qemu-devel@nongnu.org \
    --cc=thayne@realmsys.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 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.