All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Yoshinori K. Okuji" <okuji@enbug.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: grub2 ChangeLog conf/i386-pc.rmk conf/powerpc-i...
Date: Tue, 7 Aug 2007 21:19:08 +0200	[thread overview]
Message-ID: <200708072119.08147.okuji@enbug.org> (raw)
In-Reply-To: <9f50a7a00707251528x3c9c927dk8bb4fb3e956c9203@mail.gmail.com>

Hello,

On Thursday 26 July 2007 00:28, Jerone Young wrote:
> This was no mistake. So here is the thinking here (I figured this
> would come up). The multiboot heads outside of the grub directory are
> not grub specific. This gives other operating systems or programs (in
> this case GPL 3 compatible operating systems) the ability to include
> these headers and use them. They mainly contain definitions that are
> not just specific to grub, but multiboot.

First of all, thank you for the great contribution! I guess I really must 
finish writing up the specification now...

About the headers, I don't like the location, either. As I said before, the 
purpose of GRUB is not to provide a library. Even if code can be reused, this 
is out of our concern. And, more importantly, the reason why the header files 
are put under grub/ is to avoid conflicts with system headers. Although the 
probablity of having such a conflict on multiboot.h, I still prefer to 
segregate our own headers under grub.

Thanks,
Okuji



  parent reply	other threads:[~2007-08-07 19:19 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1IDUyx-00052s-AR@cvs.savannah.gnu.org>
2007-07-25 21:16 ` grub2 ChangeLog conf/i386-pc.rmk conf/powerpc-i Vesa Jääskeläinen
2007-07-25 22:28   ` Jerone Young
2007-07-30 21:23     ` Marco Gerards
2007-07-30 21:50       ` Jerone Young
2007-08-02 17:05         ` Marco Gerards
2007-08-07 19:19     ` Yoshinori K. Okuji [this message]
2007-08-07 19:48       ` Jerone Young
2007-11-10 17:39         ` Marco Gerards

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=200708072119.08147.okuji@enbug.org \
    --to=okuji@enbug.org \
    --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.