From: Jan Kiszka <jan.kiszka@siemens.com>
To: Henning Schild <henning.schild@siemens.com>
Cc: isar-users <isar-users@googlegroups.com>,
Cedric Hombourger <Cedric_Hombourger@mentor.com>
Subject: Re: [PATCH v6 0/5] linux-custom recipe rework
Date: Fri, 31 Jan 2020 10:04:49 +0100 [thread overview]
Message-ID: <49ce3f2c-6332-8b33-88b8-12bdcbdf1daa@siemens.com> (raw)
In-Reply-To: <20200131095713.36f558df@md1za8fc.ad001.siemens.net>
On 31.01.20 09:57, Henning Schild wrote:
> Hi,
>
> where did the "apt-get" go that was in the inc? A review of the
> base-apt series found custom kernel apt-gets missing in the caching,
> now my fix can not be rebased on top of this.
>
> Is it now just "regular" dpkg doing the builddeps? If that is the case
> my base-apt series does not need a fix after all.
Exactly.
Jan
--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2020-01-31 9:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-18 19:10 Jan Kiszka
2019-12-18 19:11 ` [PATCH v6 1/5] recipes-kernel/linux: make KERNEL_DEFCONFIG support in-tree defconfigs Jan Kiszka
2019-12-18 19:11 ` [PATCH v6 2/5] linux-mainline: fix stripping of .0 from the kernel version Jan Kiszka
2019-12-18 19:11 ` [PATCH v6 3/5] linux-mainline: update from 4.19.0 to 4.19.88 Jan Kiszka
2019-12-18 19:11 ` [PATCH v6 4/5] linux-custom: rewrite to no longer depend on the kernel's builddeb Jan Kiszka
2019-12-18 19:11 ` [PATCH v6 5/5] linux-mainline: Test config fragments and LINUX_VERSION_EXTENSION Jan Kiszka
2019-12-26 15:51 ` [PATCH v6 0/5] linux-custom recipe rework Baurzhan Ismagulov
2020-01-31 8:57 ` Henning Schild
2020-01-31 9:04 ` Jan Kiszka [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=49ce3f2c-6332-8b33-88b8-12bdcbdf1daa@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=Cedric_Hombourger@mentor.com \
--cc=henning.schild@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