From: Robert Millan <rmh@aybabtu.com>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: multiboot2 vs. grub2 implementation
Date: Wed, 6 Feb 2008 13:14:50 +0100 [thread overview]
Message-ID: <20080206121450.GC22114@thorin> (raw)
In-Reply-To: <1202261023.460.4.camel@k9.localnet>
On Tue, Feb 05, 2008 at 05:23:44PM -0800, walt wrote:
>
> On Tue, 2008-02-05 at 14:23 -0600, jakllsch@kollasch.net wrote:
> > On Sun, Feb 03, 2008 at 09:11:23AM -0800, walt wrote:
> > > jakllsch@kollasch.net wrote:
> > >> Hi,
> > >>
> > >> In the course of actually trying to use the MultibootDraft, I've
> > >> discovered
> > >> some places where the draft and the grub2 implementation differ...
> > >
> > > Hi Jonathan,
> > >
> > > Are you using grub2/cvs with or without Bean's latest multiboot patch?
> >
> > I tend not to be aware of these things. I'm using stock sources.
> >
> > > It still hasn't been committed, and I was about to ask about it anyway.
> > > Without that patch, multiboot doesn't work.
> >
> > Hmm.
>
> Agreed :o) Bean's patch had some whitespace corruption anyway, so here
> it is again, diffed against today's latest cvs grub2:
If you just fixed whitespace, it is better if we just use patch -l or Bean
fixes it. Otherwise it means more paperwork and legal stuff :-/
Bean, where you going to commit that patch?
--
Robert Millan
<GPLv2> I know my rights; I want my phone call!
<DRM> What use is a phone call… if you are unable to speak?
(as seen on /.)
next prev parent reply other threads:[~2008-02-06 12:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-03 16:39 multiboot2 vs. grub2 implementation jakllsch
2008-02-03 17:11 ` walt
2008-02-05 20:23 ` jakllsch
2008-02-06 1:23 ` walt
2008-02-06 12:14 ` Robert Millan [this message]
2008-02-06 15:18 ` Bean
2008-02-06 15:33 ` Robert Millan
2008-02-06 16:48 ` Robert Millan
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=20080206121450.GC22114@thorin \
--to=rmh@aybabtu.com \
--cc=grub-devel@gnu.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.