Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Patrick Ohly <patrick.ohly@intel.com>
To: ed.bartosh@linux.intel.com
Cc: Gary Thomas <gary@mlbassoc.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: Create more than one image with WIC
Date: Wed, 15 Mar 2017 14:39:18 +0100	[thread overview]
Message-ID: <1489585158.6396.102.camel@intel.com> (raw)
In-Reply-To: <20170315125810.GA28986@linux.intel.com>

On Wed, 2017-03-15 at 14:58 +0200, Ed Bartosh wrote:
> Regarding do_rm_work. It should not touch rootfs directories, I believe.

It does, and it should by default because a rootfs can be quite large.
If it's not going to be reused in another recipe, then it is worthwhile
to remove it.

-- 
Best Regards, Patrick Ohly

The content of this message is my personal opinion only and although
I am an employee of Intel, the statements I make here in no way
represent Intel's position on the issue, nor am I authorized to speak
on behalf of Intel on this matter.





  reply	other threads:[~2017-03-15 13:39 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-08  9:44 Create more than one image with WIC Daniel Schultz
2017-03-08 10:57 ` Ed Bartosh
2017-03-08 13:41   ` Gary Thomas
2017-03-08 13:43     ` Ed Bartosh
2017-03-13 16:16       ` Daniel Schultz
2017-03-14 17:11         ` Ed Bartosh
2017-03-14 17:49           ` Patrick Ohly
2017-03-14 18:06             ` Ed Bartosh
2017-03-15  7:24               ` Patrick Ohly
2017-03-15 12:58                 ` Ed Bartosh
2017-03-15 13:39                   ` Patrick Ohly [this message]
2017-03-15 13:41                     ` Patrick Ohly
2017-03-15 14:01                       ` Ed Bartosh
2017-03-15 14:47                         ` Ed Bartosh
2017-03-15 15:09                           ` Patrick Ohly
2017-03-15 15:04                         ` Patrick Ohly

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=1489585158.6396.102.camel@intel.com \
    --to=patrick.ohly@intel.com \
    --cc=ed.bartosh@linux.intel.com \
    --cc=gary@mlbassoc.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