grub-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] import multiboot1 specification in grub trunk


From: Robert Millan
Subject: Re: [PATCH] import multiboot1 specification in grub trunk
Date: Sun, 23 Aug 2009 12:39:06 +0200
User-agent: Mutt/1.5.18 (2008-05-17)

On Thu, Aug 20, 2009 at 10:56:09PM +0200, Vladimir 'phcoder' Serbinenko wrote:
> On Thu, Aug 20, 2009 at 6:28 PM, Robert Millan<address@hidden> wrote:
> > On Wed, Aug 19, 2009 at 05:38:58PM +0200, Vladimir 'phcoder' Serbinenko 
> > wrote:
> >> On Wed, Aug 19, 2009 at 5:34 PM, Robert Millan<address@hidden> wrote:
> >> > On Wed, Aug 19, 2009 at 01:54:46PM +0200, Vladimir 'phcoder' Serbinenko 
> >> > wrote:
> >> >> This is a dirty import of multiboot specification from grub1. It
> >> >> doesn't compile it unless explicitly requested since we don't have
> >> >> appropriate autoconf tests yet. The main goal is to leave no current
> >> >> documentation in grub1 trunk. Everything in this patch is copy-pasted
> >> >> from grub1
> >> >
> >> > Actually, my plan was to move this to a separate module.  I even sent a 
> >> > patch,
> >> > long ago.
> >> It would be ok with me to do so.
> >
> > Yes.  Would you like to review my patch?
> >
> +AC_INIT([Multiboot], [1], address@hidden)
> Current version of multiboot spec is 0.69. If we want to increase
> version we need to clarify few aspects first but I feel like its
> discussion should be a separate thread.

Agreed.

> Patch on ML archive is garbled (address@hidden around every @). Can
> you resend it?

Here you are.

-- 
Robert Millan

  The DRM opt-in fallacy: "Your data belongs to us. We will decide when (and
  how) you may access your data; but nobody's threatening your freedom: we
  still allow you to remove your data and not access it at all."

Attachment: convert_grub_legacy_to_multiboot.bash
Description: Text document


reply via email to

[Prev in Thread] Current Thread [Next in Thread]