From: Adithya Balakumar <Adithya.Balakumar@toshiba-tsip.com>
To: isar-users@googlegroups.com, amikan@ilbers.de
Cc: jan.kiszka@siemens.com, kazuhiro3.hayashi@toshiba.co.jp,
dinesh.kumar@toshiba-tsip.com,
shivanand.kunijadar@toshiba-tsip.com,
sai.sathujoda@toshiba-tsip.com,
adithya.balakumar@toshiba-tsip.com
Subject: [PATCH v3 0/1] Update to the latest revision of wic in scarthgap
Date: Tue, 16 Jul 2024 16:59:58 +0530 [thread overview]
Message-ID: <20240716112959.2441845-1-Adithya.Balakumar@toshiba-tsip.com> (raw)
This patch updates wic revision to a4e7334a4b87f1bb1947f6b10f71ddb445c91d0c
from the scarthgap branch of oe-core
This brings the change to set a hash_seed to generate deterministic directory
indexes while deploying empty ext filesystems for reproducible builds.
This patch is also shared with openembedded-core and accepted.
master branch commit: 0202fb594fb05098cb8d8b6088e63beb40b5906e
scarthgap branch commit: a4e7334a4b87f1bb1947f6b10f71ddb445c91d0c
Changes since v2:
Update commit message to reflect the commit id of the patch in the scarthgap
branch of OE-core.
Changes since v1:
There is no change in the patch from v1. Just that this patch is also applied
to the scarthgap branch in OE-core.
Adithya Balakumar (1):
wic: Update to the latest revision of wic in scarthgap
scripts/lib/wic/partition.py | 37 ++++++++++++++++++++++--------------
1 file changed, 23 insertions(+), 14 deletions(-)
--
2.39.2
--
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 on the web visit https://groups.google.com/d/msgid/isar-users/20240716112959.2441845-1-Adithya.Balakumar%40toshiba-tsip.com.
next reply other threads:[~2024-07-16 11:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 11:29 Adithya Balakumar [this message]
2024-07-16 11:29 ` [PATCH v3 1/1] wic: " Adithya Balakumar
2024-07-23 7:39 ` [PATCH v3 0/1] " Uladzimir Bely
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=20240716112959.2441845-1-Adithya.Balakumar@toshiba-tsip.com \
--to=adithya.balakumar@toshiba-tsip.com \
--cc=amikan@ilbers.de \
--cc=dinesh.kumar@toshiba-tsip.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=kazuhiro3.hayashi@toshiba.co.jp \
--cc=sai.sathujoda@toshiba-tsip.com \
--cc=shivanand.kunijadar@toshiba-tsip.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