From: Uladzimir Bely <ubely@ilbers.de>
To: isar-users@googlegroups.com, Jan Kiszka <jan.kiszka@siemens.com>,
Henning Schild <henning.schild@siemens.com>
Subject: Re: [RFC 0/4] PoC for isar-apt repo reusing
Date: Fri, 03 Sep 2021 11:18:55 +0300 [thread overview]
Message-ID: <25090090.1r3eYUQgxm@home> (raw)
In-Reply-To: <bc6717cb-de01-10a2-1087-9dd0c74df969@siemens.com>
In the email from пятница, 3 сентября 2021 г. 08:52:44 +03 user Jan Kiszka
wrote:
>
> Patch 1 should likely be pulled out and merged independently - not
> really an RFC, rather a fix, no?
>
Yes, it may be merged independently. Currently it works only due to the empty
contents of the overlapped task.
In the email from четверг, 2 сентября 2021 г. 14:11:45 +03 user Henning Schild
wrote:
>
> If you want i guess Adriaan can share the current state of the "sstate"
> patch series for anyone to play with.
>
Yes, if you share these patches, we could look at them to see the idea and
possible overlaps of this PoC functionality.
--
Uladzimir Bely
Promwad Ltd.
External service provider of ilbers GmbH
Maria-Merian-Str. 8
85521 Ottobrunn, Germany
+49 (89) 122 67 24-0
Commercial register Munich, HRB 214197
General Manager: Baurzhan Ismagulov
prev parent reply other threads:[~2021-09-03 8:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 9:58 Uladzimir Bely
2021-09-02 9:58 ` [RFC 1/4] meta-isar: Fix do_dpkg_build override for prebuild-deb recipe Uladzimir Bely
2021-09-02 9:58 ` [RFC 2/4] isar-apt: PoC of reusing isar-apt repo Uladzimir Bely
2021-09-02 9:58 ` [RFC 3/4] ci: Test for isar-apt reuse Uladzimir Bely
2021-09-02 9:58 ` [RFC 4/4] doc: Add section for isar-apt reuse functionality Uladzimir Bely
2021-09-02 11:11 ` [RFC 0/4] PoC for isar-apt repo reusing Henning Schild
2021-09-03 8:43 ` Baurzhan Ismagulov
2021-09-03 5:52 ` Jan Kiszka
2021-09-03 8:18 ` Uladzimir Bely [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=25090090.1r3eYUQgxm@home \
--to=ubely@ilbers.de \
--cc=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