From: Anton Mikanovich <amikan@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Badrikesh Prusty <badrikesh.prusty@siemens.com>,
isar-users@googlegroups.com,
Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: Re: [PATCH] meta: default "Rules-Requires-Root: no", make it configurable
Date: Wed, 17 Sep 2025 11:26:24 +0300 [thread overview]
Message-ID: <76edc5be-e4b2-4a8a-9154-99b71883f16e@ilbers.de> (raw)
In-Reply-To: <574e0dbd-9465-4fde-94c3-7178d8f13496@siemens.com>
17/09/2025 11:18, Jan Kiszka wrote:
> Hi Anton,
>
> I see this patch in your test queue but it's not ready for upstream yet
> - just to avoid that it accidentally lands in next.
>
> Jan
>
Hello Jan,
Thanks for keeping an eye on it, I'm just trying to find unbuildable patches
as early as possible, so sometimes CI is running even before looking
inside of
the patch contents or discussions. Will wait for work on it to be finished.
P.S. I hope we will went to automatic input control sometimes.
--
You received this message because you are subscribed to the Google Groups "isar-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to isar-users+unsubscribe@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/isar-users/76edc5be-e4b2-4a8a-9154-99b71883f16e%40ilbers.de.
next prev parent reply other threads:[~2025-09-17 8:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-07 20:42 'Badrikesh Prusty' via isar-users
2025-09-07 20:54 ` 'Badrikesh Prusty' via isar-users
2025-09-08 5:28 ` 'Jan Kiszka' via isar-users
2025-09-08 8:02 ` 'Felix Moessbauer' via isar-users
2025-09-11 9:43 ` 'Prusty, Badrikesh' via isar-users
2025-09-17 8:18 ` 'Jan Kiszka' via isar-users
2025-09-17 8:26 ` Anton Mikanovich [this message]
2025-09-17 8:28 ` 'Jan Kiszka' via isar-users
2025-09-19 6:32 ` 'Badrikesh Prusty' via isar-users
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=76edc5be-e4b2-4a8a-9154-99b71883f16e@ilbers.de \
--to=amikan@ilbers.de \
--cc=badrikesh.prusty@siemens.com \
--cc=felix.moessbauer@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