From: Alexander Dahl <ada@thorsis.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH 0/3] Minor build improvements
Date: Thu, 27 Feb 2020 15:44:46 +0100 [thread overview]
Message-ID: <20200227144449.29660-1-ada@thorsis.com> (raw)
Hei hei,
small series of three patches.
1. The patch for the opkg package addresses a thing which annoyed me
for years when using opkg packages. O:-)
2. The second and third patch replaces the dates put into
'/etc/os-release' and '/etc/issue' by reproducible ones. I just
searched for invocations of `date` in make rules and fixed those two.
There's at least one other related to rauc, which I could not test
easily, so I skipped that one.
Greets
Alex
Alexander Dahl (3):
opkg: Regenerate config after input variable changes
os-release: Make date string reproducible
rootfs: issue: Make date string reproducible
rules/opkg.make | 14 ++++++++++++++
rules/os-release.make | 2 +-
rules/rootfs.make | 2 +-
3 files changed, 16 insertions(+), 2 deletions(-)
--
2.20.1
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
next reply other threads:[~2020-02-27 14:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 14:44 Alexander Dahl [this message]
2020-02-27 14:44 ` [ptxdist] [PATCH 1/3] opkg: Regenerate config after input variable changes Alexander Dahl
2020-03-20 11:31 ` Michael Olbrich
2020-03-27 13:24 ` Michael Olbrich
2020-02-27 14:44 ` [ptxdist] [PATCH 2/3] os-release: Make date string reproducible Alexander Dahl
2020-02-28 10:16 ` Roland Hieber
2020-02-28 15:40 ` Roland Hieber
2020-02-28 16:14 ` Alexander Dahl
2020-02-29 8:48 ` Michael Olbrich
2020-02-29 17:41 ` Alexander Dahl
2020-03-20 11:38 ` Michael Olbrich
2020-02-27 14:44 ` [ptxdist] [PATCH 3/3] rootfs: issue: " Alexander Dahl
2020-03-20 11:39 ` Michael Olbrich
2020-03-20 12:08 ` Alexander Dahl
2020-03-20 12:44 ` Michael Olbrich
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=20200227144449.29660-1-ada@thorsis.com \
--to=ada@thorsis.com \
--cc=ptxdist@pengutronix.de \
/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