RFC Include timezone information in build
Get series with b4
b4 am 20150508210502.GU5267@bill-the-catVersions newest first
- v1 RFC Latest0 of 1 patch 0 repliesNew
Patches in v1 No applies recorded yet
The patch the cover letter announces is not in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [U-Boot] [RFC PATCH v1 0/1] Include timezone information in build
Quoted 11 lines · Chris Packham
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.
Quoted 8 lines
This is my attempt to address the issue by defining
U_BOOT_TZalong sideU_BOOT_TIMEandU_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.
Concept is fine, I'd actually prefer %z so that the size increase is constant at least. Please do that in a non-RFC v2 and I'll pick it up, thanks!
Signature · 8 lines
Tom -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: Digital signature URL: <http://lists.denx.de/pipermail/u-boot/attachments/20150508/b8c86d16/attachment.sig>