From: venkata.pyla@toshiba-tsip.com
To: isar-users@googlegroups.com
Cc: venkata pyla <venkata.pyla@toshiba-tsip.com>,
amikan@ilbers.de, jan.kiszka@siemens.com,
henning.schild@siemens.com, kazuhiro3.hayashi@toshiba.co.jp,
dinesh.kumar@toshiba-tsip.com
Subject: [PATCH v4 0/1] Fix for reproducible build issue v4
Date: Mon, 9 Jan 2023 21:35:45 +0530 [thread overview]
Message-ID: <20230109160546.26339-1-venkata.pyla@toshiba-tsip.com> (raw)
From: venkata pyla <venkata.pyla@toshiba-tsip.com>
Hi,
Chages from v3:
- bbwarn only file type for modified timestamps and exlcude others like directories, links and char files as they are obvious changes for modified file timestamps.
venkata pyla (1):
image.bbclass: fix non-reproducible file time-stamps inside rootfs
meta-isar/conf/local.conf.sample | 10 ++++++++++
meta/classes/image.bbclass | 10 ++++++++++
2 files changed, 20 insertions(+)
--
2.20.1
next reply other threads:[~2023-01-09 16:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 16:05 venkata.pyla [this message]
2023-01-09 16:05 ` [PATCH v4 1/1] image.bbclass: fix non-reproducible file time-stamps inside rootfs venkata.pyla
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=20230109160546.26339-1-venkata.pyla@toshiba-tsip.com \
--to=venkata.pyla@toshiba-tsip.com \
--cc=amikan@ilbers.de \
--cc=dinesh.kumar@toshiba-tsip.com \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.com \
--cc=jan.kiszka@siemens.com \
--cc=kazuhiro3.hayashi@toshiba.co.jp \
/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