Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: Jingdong.Lu@windriver.com
Subject: Re: [PATCH 0/1]initrdscripts: fix init-live.sh for hddimg and livecd
Date: Wed, 24 Aug 2011 16:10:36 -0700	[thread overview]
Message-ID: <4E5584EC.7060600@linux.intel.com> (raw)
In-Reply-To: <cover.1314172740.git.jingdong.lu@windriver.com>

On 08/24/2011 01:25 AM, Jingdong.Lu@windriver.com wrote:
> From: Jingdong Lu<jingdong.lu@windriver.com>
>
> Both hddimg and livecd use init-live.sh script to boot the rootfs.img.
> But the paths of rootfs.img in hddimg and livecd are different. So we add
> a variable "ISOLINUX" to provide a correct path.
>
> The following changes since commit edd8e1e8b974eb3f0f9f66c2207aadf43612350b:
>    Scott Rifenbark (1):
>          documentation/adt-manual/adt-command.xml: general edits.
>
> are available in the git repository at:
>
>    git://git.pokylinux.org/poky-contrib jingdonglu/bug686-v2
>    http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=jingdonglu/bug686-v2
>
> Jingdong Lu (1):
>    initrdscripts: fix init-live.sh for hddimg and livecd
>
>   meta/recipes-core/initrdscripts/files/init-live.sh |   17 +++++++++++------
>   .../initrdscripts/initramfs-live-boot_1.0.bb       |    2 +-
>   2 files changed, 12 insertions(+), 7 deletions(-)
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>

Merged into OE-Core

Thanks
	Sau!



      parent reply	other threads:[~2011-08-24 23:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-24  8:25 [PATCH 0/1]initrdscripts: fix init-live.sh for hddimg and livecd Jingdong.Lu
2011-08-24  8:25 ` [PATCH 1/1] initrdscripts: " Jingdong.Lu
2011-08-24 15:43   ` Otavio Salvador
2011-08-24 23:10 ` Saul Wold [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=4E5584EC.7060600@linux.intel.com \
    --to=sgw@linux.intel.com \
    --cc=Jingdong.Lu@windriver.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