public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Henning Schild <henning.schild@siemens.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: <isar-users@googlegroups.com>
Subject: Re: [PATCHv2 0/9] a few cleanups a bug and a feature
Date: Thu, 7 Nov 2019 15:36:32 +0100	[thread overview]
Message-ID: <20191107153632.1b01020c@md1za8fc.ad001.siemens.net> (raw)
In-Reply-To: <468c9206-6fd0-2c2f-51d0-f44678ab89f9@siemens.com>

Am Thu, 7 Nov 2019 13:16:09 +0100
schrieb Jan Kiszka <jan.kiszka@siemens.com>:

> On 23.10.19 13:42, [ext] Henning Schild wrote:
> > From: Henning Schild <henning.schild@siemens.com>
> > 
> > The first 6 patches are pure cosmetic to clean up some things i
> > stumbled over when working on base-apt. I have a few more but they
> > will come later.
> > 
> > The series introduces the feature that Isar respects BB_NO_NETWORK,
> > p7+8.
> > 
> > An the final patch fixes a bug when using a not signed base-apt.
> > 
> > Henning Schild (9):
> >   rootfs: fix incorrect feature name in comment
> >   base-apt: use the "basename" command instead of pattern
> > substitution base_apt_helper: change variable names to increase
> > readability rootfs: rename ROOTFS_INSTALL_COMMAND lock to
> > "isar-apt-lock" dpkg-base: remove pointless ";" s at end of line
> >   dpkg-base: fix indentation from tabs to spaces
> >   base: implement BB_NO_NETWORK for apt-get
> >   meta: do not equip rootfss with resolv.conf when BB_NO_NETWORK
> >   bootstrap: fix debootstrap gpg issue when base-apt is not signed
> > 
> >  meta/classes/base-apt-helper.bbclass          | 14 ++++----
> >  meta/classes/base.bbclass                     | 14 ++++++++
> >  meta/classes/buildchroot.bbclass              | 10 ++++--
> >  meta/classes/dpkg-base.bbclass                | 34
> > +++++++++---------- meta/classes/dpkg-gbp.bbclass                 |
> >  2 +- meta/classes/dpkg.bbclass                     |  4 +--
> >  meta/classes/image-tools-extension.bbclass    |  2 +-
> >  meta/classes/rootfs.bbclass                   | 17 ++++++----
> >  .../isar-bootstrap/isar-bootstrap.inc         | 12 +++----
> >  meta/recipes-kernel/linux/linux-custom.inc    |  4 +--
> >  10 files changed, 66 insertions(+), 47 deletions(-)
> >   
> 
> Dropping patch 2, I've done some pre-integration in
> https://github.com/siemens/isar/commits/jan/next to accelerate
> testing.

Seems you also excluded p7, which is good. Btw all the patches i send
have passed internal and ilbers CI are usually available on my github
as well.

This stuff
https://github.com/henning-schild-work/isar/commits/henning/staging1

Henning

> Jan
> 


      reply	other threads:[~2019-11-07 14:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-23 11:42 Henning Schild
2019-10-23 11:42 ` [PATCHv2 1/9] rootfs: fix incorrect feature name in comment Henning Schild
2019-10-23 11:42 ` [PATCHv2 2/9] base-apt: use the "basename" command instead of pattern substitution Henning Schild
2019-10-23 20:36   ` Baurzhan Ismagulov
2019-10-24  9:16     ` Henning Schild
2019-10-24 12:01       ` Baurzhan Ismagulov
2019-10-24  9:34     ` chombourger
2019-10-24 12:01       ` Baurzhan Ismagulov
2019-10-23 11:42 ` [PATCHv2 3/9] base_apt_helper: change variable names to increase readability Henning Schild
2019-10-23 11:42 ` [PATCHv2 4/9] rootfs: rename ROOTFS_INSTALL_COMMAND lock to "isar-apt-lock" Henning Schild
2019-10-23 11:42 ` [PATCHv2 5/9] dpkg-base: remove pointless ";" s at end of line Henning Schild
2019-10-23 11:42 ` [PATCHv2 6/9] dpkg-base: fix indentation from tabs to spaces Henning Schild
2019-10-23 11:42 ` [PATCHv2 7/9] base: implement BB_NO_NETWORK for apt-get Henning Schild
2019-10-31  8:42   ` Henning Schild
2019-10-23 11:42 ` [PATCHv2 8/9] meta: do not equip rootfss with resolv.conf when BB_NO_NETWORK Henning Schild
2019-10-23 11:42 ` [PATCHv2 9/9] bootstrap: fix debootstrap gpg issue when base-apt is not signed Henning Schild
2019-10-23 11:43 ` [PATCHv2 0/9] a few cleanups a bug and a feature Henning Schild
2019-11-07 12:16 ` Jan Kiszka
2019-11-07 14:36   ` Henning Schild [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=20191107153632.1b01020c@md1za8fc.ad001.siemens.net \
    --to=henning.schild@siemens.com \
    --cc=isar-users@googlegroups.com \
    --cc=jan.kiszka@siemens.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