public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: "[ext] claudius.heine.ext@siemens.com" <claudius.heine.ext@siemens.com>
Cc: <isar-users@googlegroups.com>, Claudius Heine <ch@denx.de>
Subject: Re: [PATCH v2 0/2] Use fetcher for images
Date: Thu, 21 Sep 2017 14:25:57 +0200	[thread overview]
Message-ID: <20170921142557.52a7358d@md1em3qc> (raw)
In-Reply-To: <20170921111911.8133-1-claudius.heine.ext@siemens.com>

Looks good to me.

Henning

Am Thu, 21 Sep 2017 13:19:09 +0200
schrieb "[ext] claudius.heine.ext@siemens.com"
<claudius.heine.ext@siemens.com>:

> From: Claudius Heine <ch@denx.de>
> 
> Hi,
> 
> I splitted those patches up.
> 
> Now the first patch addresses the 'install -d' style issue and the
> second is the main patch that changes the tasks to use the bitbake
> fetchers.
> 
> Cheers,
> Claudius
> 
> Claudius Heine (2):
>   isar-image-base & buildchroot: create hooks_multistrap dir with bb
>     flag
>   meta-isar/isar-image-base and meta/buildchroot: Use fetcher for
> files
> 
>  meta-isar/recipes-core/images/isar-image-base.bb | 41
> +++++++++++++-----------
> meta/recipes-devtools/buildchroot/buildchroot.bb | 34
> +++++++++++--------- 2 files changed, 40 insertions(+), 35
> deletions(-)
> 


  parent reply	other threads:[~2017-09-21 12:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-21 11:19 claudius.heine.ext
2017-09-21 11:19 ` [PATCH v2 1/2] isar-image-base & buildchroot: create hooks_multistrap dir with bb flag claudius.heine.ext
2017-09-21 11:19 ` [PATCH v2 2/2] meta-isar/isar-image-base and meta/buildchroot: Use fetcher for files claudius.heine.ext
2017-09-21 12:25 ` Henning Schild [this message]
2017-09-25 12:32 ` [PATCH v2 0/2] Use fetcher for images Alexander Smirnov

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=20170921142557.52a7358d@md1em3qc \
    --to=henning.schild@siemens.com \
    --cc=ch@denx.de \
    --cc=claudius.heine.ext@siemens.com \
    --cc=isar-users@googlegroups.com \
    /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