From: Robert Millan <rmh@aybabtu.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Multiboot 2 branch (Re: [RFC] Tagged mbi)
Date: Thu, 7 Jan 2010 22:16:50 +0100 [thread overview]
Message-ID: <20100107211650.GB26340@thorin> (raw)
In-Reply-To: <4B4259D3.5020004@gmail.com>
On Mon, Jan 04, 2010 at 10:12:51PM +0100, Vladimir 'φ-coder/phcoder' Serbinenko wrote:
> --- include/multiboot.h 2010-01-02 17:50:06 +0000
> +++ include/multiboot.h 2010-01-02 21:06:42 +0000
> @@ -31,8 +31,11 @@
> /* This should be in %eax. */
> #define MULTIBOOT_BOOTLOADER_MAGIC 0x2BADB002
>
> +/* This should be in %eax. */
> +#define MULTIBOOT_BOOTLOADER_MAGIC_TAGGED 0x3BADB002
I created a branch for backward-incompatible changes, it's in
/branches/multiboot2.
This does NOT mean that backward-incompatible changes are postponed. The
draft in /branches/multiboot2 is already implemented in latest GRUB trunk.
Further changes to this draft can be implemented in GRUB inmediately.
So the workflow is basically:
- Non-incompatible ammendments can go in /trunk/multiboot.
- Incompatible ammendments can go in /branches/multiboot2. This branch
can (and should) be periodically resynced with /trunk/multiboot.
- In both cases, ammendments should be accompanied by changes to the
example kernel (when this makes sense, of course).
- The master copies of multiboot.h and multiboot2.h are in those
respective branches. GRUB shouldn't need to diverge from them, as
all the GRUB-specific declarations are split in <grub/*> namespace
already.
--
Robert Millan
"Be the change you want to see in the world" -- Gandhi
prev parent reply other threads:[~2010-01-07 21:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-04 21:12 [RFC] Tagged mbi Vladimir 'φ-coder/phcoder' Serbinenko
2010-01-07 21:08 ` Robert Millan
2010-01-07 21:32 ` Vladimir 'φ-coder/phcoder' Serbinenko
2010-01-07 21:16 ` Robert Millan [this message]
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=20100107211650.GB26340@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.