From: Anton Mikanovich <amikan@ilbers.de>
To: Jan Kiszka <jan.kiszka@siemens.com>, isar-users@googlegroups.com
Subject: Re: [PATCH v4 4/4] installer: Fix DEPLOY_DIR_IMAGE path for target image
Date: Fri, 23 Jan 2026 14:44:26 +0200 [thread overview]
Message-ID: <1a9c6ac9-6e6c-4837-b08b-bff003c19226@ilbers.de> (raw)
In-Reply-To: <6d3d3b78-d29c-43c6-ac83-dbdc72b1539f@siemens.com>
21/01/2026 20:29, Jan Kiszka wrote:
> Than fix the patch that is changing it, or you are creating a friction
> point for bisection.
>
> Jan
Hello Jan,
This patch is related only to installer which was never changed in the
patchset
before. I don't think squashing all the changes to one commit will be a good
idea.
--
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/1a9c6ac9-6e6c-4837-b08b-bff003c19226%40ilbers.de.
next prev parent reply other threads:[~2026-01-23 12:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 15:30 [PATCH v4 0/4] Deploy DTBs with separate recipe Anton Mikanovich
2026-01-21 15:30 ` [PATCH v4 1/4] meta: Fix do_copy_boot_files error for different distros of same machine Anton Mikanovich
2026-01-21 15:30 ` [PATCH v4 2/4] testsuite: Add test to check dtb deployment Anton Mikanovich
2026-01-21 15:30 ` [PATCH v4 3/4] meta: Move DTB deployment to a separate dtb-files recipe Anton Mikanovich
2026-01-21 18:27 ` 'Jan Kiszka' via isar-users
2026-01-23 12:40 ` Anton Mikanovich
2026-01-23 14:24 ` 'Jan Kiszka' via isar-users
2026-01-21 15:30 ` [PATCH v4 4/4] installer: Fix DEPLOY_DIR_IMAGE path for target image Anton Mikanovich
2026-01-21 18:29 ` 'Jan Kiszka' via isar-users
2026-01-23 12:44 ` Anton Mikanovich [this message]
2026-01-23 14:26 ` 'Jan Kiszka' via isar-users
2026-01-22 16:53 ` [PATCH v4 0/4] Deploy DTBs with separate recipe Zhihang Wei
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=1a9c6ac9-6e6c-4837-b08b-bff003c19226@ilbers.de \
--to=amikan@ilbers.de \
--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