Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Rongqing Li <rongqing.li@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] image_types_uboot: remove the middle file
Date: Thu, 2 Jul 2015 10:44:24 +0800	[thread overview]
Message-ID: <5594A588.1040901@windriver.com> (raw)
In-Reply-To: <1435804469-14774-1-git-send-email-rongqing.li@windriver.com>

drop it, I will rework the commit header

-R

On 2015年07月02日 10:34, rongqing.li@windriver.com wrote:
> From: Yue Tao <Yue.Tao@windriver.com>
>
> The .gz, .bz2 or .lzma are middle files for making gz.u-boot,
> bz2.u-boot, or lzma.u-boot. It should be removed once the final
> image is generated. Otherwise, even you --enable-rm-oldimgs=yes,
> it can't be removed, moreover more and more middle files are
> genrated via 'make fs
>
> Signed-off-by: Yue Tao <Yue.Tao@windriver.com>
> ---
>   meta/classes/image_types_uboot.bbclass | 1 +
>   1 file changed, 1 insertion(+)
>
> diff --git a/meta/classes/image_types_uboot.bbclass b/meta/classes/image_types_uboot.bbclass
> index 07837b5..dba9293 100644
> --- a/meta/classes/image_types_uboot.bbclass
> +++ b/meta/classes/image_types_uboot.bbclass
> @@ -3,6 +3,7 @@ inherit image_types kernel-arch
>   oe_mkimage () {
>       mkimage -A ${UBOOT_ARCH} -O linux -T ramdisk -C $2 -n ${IMAGE_NAME} \
>           -d ${DEPLOY_DIR_IMAGE}/$1 ${DEPLOY_DIR_IMAGE}/$1.u-boot
> +    rm $1
>   }
>
>   COMPRESSIONTYPES += "gz.u-boot bz2.u-boot lzma.u-boot u-boot"
>

-- 
Best Reagrds,
Roy | RongQing Li


  reply	other threads:[~2015-07-02  2:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-02  2:34 [PATCH] image_types_uboot: remove the middle file rongqing.li
2015-07-02  2:44 ` Rongqing Li [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-07-02  7:18 rongqing.li

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=5594A588.1040901@windriver.com \
    --to=rongqing.li@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