From: Peter Kjellerstedt <peter.kjellerstedt@axis.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 0/1] Make ${DATE} and ${TIME} consistent
Date: Fri, 6 Sep 2013 17:53:19 +0200 [thread overview]
Message-ID: <cover.1378482725.git.pkj@axis.com> (raw)
This fixes a problem with ${DATE} and ${TIME} not being consistent
between different workers. E.g., a fakerooted task had a different time
than a non-fakerooted one...
//Peter
The following changes since commit ed3ef0823fde89371a473d20c0127c0bd16d062b:
qemumips: fix keyboard entry in graphical boots (2013-09-05 16:27:54 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib pkj/consistent_date_and_time
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=pkj/consistent_date_and_time
Peter Kjellerstedt (1):
bitbake: Ensure ${DATE} and ${TIME} are consistent
bitbake/bin/bitbake-worker | 2 ++
bitbake/lib/bb/runqueue.py | 2 ++
2 files changed, 4 insertions(+)
--
1.8.2.1
next reply other threads:[~2013-09-06 15:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-06 15:53 Peter Kjellerstedt [this message]
2013-09-06 15:53 ` [PATCH 1/1] bitbake: Ensure ${DATE} and ${TIME} are consistent Peter Kjellerstedt
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=cover.1378482725.git.pkj@axis.com \
--to=peter.kjellerstedt@axis.com \
--cc=bitbake-devel@lists.openembedded.org \
/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