From: Silvano Cirujano Cuesta <silvano.cirujano-cuesta@siemens.com>
To: Jan Kiszka <jan.kiszka@siemens.com>, isar-users@googlegroups.com
Subject: Re: [RFC PATCH 0/2] support generation of sdk container images
Date: Fri, 15 Jan 2021 09:16:59 +0100 [thread overview]
Message-ID: <dc312099-a031-c94b-f988-a4afcb5b9554@siemens.com> (raw)
In-Reply-To: <5446e5ec-e0b5-b382-eaea-39a5159ea216@siemens.com>
On 15/01/2021 08:09, Jan Kiszka wrote:
> On 14.01.21 14:56, [ext] Silvano Cirujano Cuesta wrote:
>> I wonder how to interpret the current feelings about this proposal:
>>
>> * There's no interest at all.
>>
>> * I haven't succeed on raising enough interest. In that case I'd need more input from people who see the demand for this functionality to better understand what's missing in my proposal.
>>
>> * There's interest, but I should update the patch according the comments up-to-now before I send a 1st patch series proposal (or a 2nd RFC).
>>
>> I'd appreciate any feedback. The more decision power the person giving the feedback, the more valuable it is for me :-)
>>
> The level of feedback you received is already quite good for a first
> round :), and there is usually no early feedback from maintainers.
I don't meant that the feedback was bad, only mostly opposed :-)
> I would say update the series, addressing that smaller issue(s) and
> remove the RFC. I'll also give that a try soon.
This is enough feedback to confirm me on moving forward. My next steps are then: addressing the small issues and adding in the cover letter information on how to easily test it.
Silvano
>
> Thanks a lot,
> Jan
>
--
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2021-01-15 8:17 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-12 10:33 Silvano Cirujano Cuesta
2021-01-12 10:33 ` [RFC PATCH 1/2] sdk: support creation of container image Silvano Cirujano Cuesta
2021-01-12 11:36 ` Henning Schild
2021-01-12 11:50 ` Silvano Cirujano Cuesta
2021-01-12 14:50 ` Jan Kiszka
2021-01-12 17:08 ` Silvano Cirujano Cuesta
2021-01-12 17:36 ` Henning Schild
2021-01-12 17:54 ` Silvano Cirujano Cuesta
2021-01-12 18:04 ` Jan Kiszka
2021-01-12 20:46 ` Silvano Cirujano Cuesta
2021-01-12 10:33 ` [RFC PATCH 2/2] docs: document usage of sdk container images Silvano Cirujano Cuesta
2021-01-12 11:40 ` Henning Schild
2021-01-12 12:03 ` Silvano Cirujano Cuesta
2021-01-12 12:18 ` Henning Schild
2021-01-12 14:52 ` Silvano Cirujano Cuesta
2021-01-12 14:56 ` Jan Kiszka
2021-01-12 15:12 ` Silvano Cirujano Cuesta
2021-01-12 15:14 ` Jan Kiszka
2021-01-12 15:11 ` Henning Schild
2021-01-12 16:26 ` Silvano Cirujano Cuesta
2021-01-14 13:56 ` [RFC PATCH 0/2] support generation " Silvano Cirujano Cuesta
2021-01-14 18:32 ` Henning Schild
2021-01-15 8:11 ` Silvano Cirujano Cuesta
2021-01-15 7:09 ` Jan Kiszka
2021-01-15 8:16 ` Silvano Cirujano Cuesta [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=dc312099-a031-c94b-f988-a4afcb5b9554@siemens.com \
--to=silvano.cirujano-cuesta@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