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
_______________________________________________
Grub-devel mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/grub-devel
