All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marco Gerards <mgerards@xs4all.nl>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: grub2 ChangeLog conf/i386-pc.rmk conf/powerpc-i...
Date: Thu, 02 Aug 2007 19:05:29 +0200	[thread overview]
Message-ID: <87sl71989y.fsf@xs4all.nl> (raw)
In-Reply-To: <9f50a7a00707301450j492ada8bne05b2e574f44367@mail.gmail.com> (Jerone Young's message of "Mon, 30 Jul 2007 16:50:01 -0500")

"Jerone Young" <jerone@gmail.com> writes:

> On 7/30/07, Marco Gerards <mgerards@xs4all.nl> wrote:
>> "Jerone Young" <jerone@gmail.com> writes:
>>
>> > 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.
>>
>> It would be better to discuss such things on the list first, clearly.
>> The directory structure is, unfortunately, quite permanent in CVS and
>> difficult to change properly.
>>
>> How about using include/multiboot/*.h instead?
>
> That could work also. Having include/multiboot/*.h wouldn't hurt.
> Though is it necessary to have everything in it's own directory under
> the include directory? I'm in favor either way.

It is not a big issue for me and changing it now would make it messy
with CVS, I think.  It depends on what the other developers think.

--
Marco




  reply	other threads:[~2007-08-02 17:03 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 [this message]
2007-08-07 19:19     ` Yoshinori K. Okuji
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=87sl71989y.fsf@xs4all.nl \
    --to=mgerards@xs4all.nl \
    --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.