From: Tom Zanussi <tom.zanussi@intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/2] Add new recipes for grub2
Date: Wed, 14 Sep 2011 11:01:15 -0500 [thread overview]
Message-ID: <1316016075.26879.2487.camel@elmorro> (raw)
In-Reply-To: <CAP9ODKpsEx=05bVBVYvxLhuDfb=14gdZ2KaERrWCkHQYQOfHpQ@mail.gmail.com>
On Wed, 2011-09-14 at 08:55 -0700, Otavio Salvador wrote:
> On Wed, Sep 14, 2011 at 12:45, Tom Zanussi <tom.zanussi@intel.com> wrote:
> > On Wed, 2011-09-14 at 05:30 -0700, Otavio Salvador wrote:
> >> On Wed, Sep 14, 2011 at 02:39, Tom Zanussi <tom.zanussi@intel.com> wrote:
> >> /> A future patch will factor out the common parts of init_install_2.0.sh
> >> > with init_install 1.0 - this initial patchset essentially just fixes
> >> > what's necessary for YOCTO bug #1428 in order to get things working again.
> >>
> >> Wouldn't be better to drop 1.0 completely?
> >>
> >
> > You're right, and the original did do that essentially - on second
> > thought it was much simpler - I'll resubmit something like that...
>
> I prefer to have 1.0 dropped since it avoids duplicated maintainence
> work and support. Besides, since this is gonna be a base of newer
> Yocto we ought to ensure that the layers do get their bsp updated
> (even thought I think the only user of it is meta-intel at this
> moment).
>
Well, my new version handles both grub 0.97 and grub2. We need to keep
grub 0.97 around because grub2 is GPLv3.
Tom
> Nice that you agree with it.
>
next prev parent reply other threads:[~2011-09-14 16:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-14 5:39 [PATCH 0/2] Add new recipes for grub2 Tom Zanussi
2011-09-14 12:30 ` Otavio Salvador
2011-09-14 15:45 ` Tom Zanussi
2011-09-14 15:55 ` Otavio Salvador
2011-09-14 16:01 ` Tom Zanussi [this message]
2011-09-14 16:05 ` Otavio Salvador
2011-09-14 16:07 ` Tom Zanussi
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=1316016075.26879.2487.camel@elmorro \
--to=tom.zanussi@intel.com \
--cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox