From: Baurzhan Ismagulov <ibr@radix50.net>
To: isar-users@googlegroups.com
Cc: Jan Kiszka <jan.kiszka@siemens.com>
Subject: Re: [PATCH] image-account-extension: Also rebuild roots on GROUP_* changes
Date: Thu, 17 Jul 2025 12:30:00 +0200 [thread overview]
Message-ID: <aHjQqBlEFEgdnXl2@abai.de> (raw)
In-Reply-To: <76ea2330-5b4b-46ab-9d35-3bc9c64ea6a5@siemens.com>
On 2025-07-16 21:51, 'Jan Kiszka' via isar-users wrote:
> > Unlike what 3330e1ca2bca what assumed, also certain changes to groups
> > can invalidate previous runs of the account extensions against the
> > cached rootfs.
>
> This seems to have been forgotten.
Not forgotten, we just have a bit of backlog at the moment.
Applied to next, thanks.
With kind regards,
Baurzhan
--
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/aHjQqBlEFEgdnXl2%40abai.de.
prev parent reply other threads:[~2025-07-17 10:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-18 6:57 'Jan Kiszka' via isar-users
2025-07-16 19:51 ` 'Jan Kiszka' via isar-users
2025-07-17 8:44 ` 'MOESSBAUER, Felix' via isar-users
2025-07-17 10:30 ` Baurzhan Ismagulov [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=aHjQqBlEFEgdnXl2@abai.de \
--to=ibr@radix50.net \
--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