From: Chris Packham <judge.packham@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC PATCH v1 0/1] Include timezone information in build
Date: Thu, 30 Apr 2015 12:38:22 +1200 [thread overview]
Message-ID: <1430354303-30200-1-git-send-email-judge.packham@gmail.com> (raw)
Hi,
Recently an eagle-eyed tester pointed out to me that the build time
reported in my u-boot build did not match the file timestamp on the
server it was stored on. This is because at $dayjob we have a build farm
with times set to UTC while the storage server was displaying the local
time. In reality the times were the same but the timezones were not and
there is no indication in the u-boot version about how to interpret the
time.
This is my attempt to address the issue by defining U_BOOT_TZ along side
U_BOOT_TIME and U_BOOT_DATE. I've kept the TZ portion separate because I
thought there might some push pack on changing the version string. For
my purposes I can display the TZ separately as long as it is defined by
the build process. I've also elected to use %Z instead of %z as I feel
that the timezone name is more friendly but that's just a personal
preference so I wouldn't object to switching to the numeric
representation if others feel strongly.
Chris Packham (1):
Makefile: Add U_BOOT_TZ and include in version
Makefile | 3 ++-
include/version.h | 2 +-
2 files changed, 3 insertions(+), 2 deletions(-)
--
2.3.5
next reply other threads:[~2015-04-30 0:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-30 0:38 Chris Packham [this message]
2015-04-30 0:38 ` [U-Boot] [RFC PATCH v1] Makefile: Add U_BOOT_TZ and include in version Chris Packham
2015-05-06 5:38 ` Chris Packham
2015-05-06 15:01 ` Simon Glass
2015-05-10 9:02 ` [U-Boot] [PATCH v2] " Chris Packham
2015-05-28 13:23 ` [U-Boot] [U-Boot, " Tom Rini
2015-05-08 21:05 ` [U-Boot] [RFC PATCH v1 0/1] Include timezone information in build Tom Rini
2015-05-10 9:28 ` Chris Packham
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=1430354303-30200-1-git-send-email-judge.packham@gmail.com \
--to=judge.packham@gmail.com \
--cc=u-boot@lists.denx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.