Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] initscripts: Properly handle new timestamp format
Date: Thu, 01 Mar 2012 14:59:08 +0000	[thread overview]
Message-ID: <1330613948.31767.12.camel@ted> (raw)
In-Reply-To: <1330612994-26329-1-git-send-email-gary@mlbassoc.com>

On Thu, 2012-03-01 at 07:43 -0700, Gary Thomas wrote:
> Recent changes have attempted to make consistant use of /etc/timestamp
> In particular
>   5aab665 initscripts: Make /etc/timestamp consistent again.
>   173a48f image.bbclass: Ensure timestamp matches format used in initscripts after recent changes
> 
> This new format can cause problems as the value is too large for
> most [32 bit] machines.  Work around this by only comparing the
> YYYYMMDD portion (which does fit in 32 bits).  Also, the new format
> is not directly compatible with the 'date' command line, so it
> must be reformatted for use.
> 
> Signed-off-by: Gary Thomas <gary@mlbassoc.com>
> ---
>  .../initscripts/initscripts-1.0/bootmisc.sh        |    4 ++--
>  1 files changed, 2 insertions(+), 2 deletions(-)

I merged the changes to busybox in relation to this. Is this patch still
needed?

Cheers,

Richard




  reply	other threads:[~2012-03-01 15:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-01 14:43 [PATCH] initscripts: Properly handle new timestamp format Gary Thomas
2012-03-01 14:59 ` Richard Purdie [this message]
2012-03-01 15:11   ` Gary Thomas
2012-03-01 15:27     ` Gary Thomas
2012-03-01 15:44       ` Richard Purdie
2012-03-01 15:52         ` Gary Thomas
2012-03-01 16:04           ` Otavio Salvador
2012-03-01 16:06             ` Gary Thomas
2012-03-02  6:15               ` Lauri Hintsala
2012-03-01 16:01       ` Otavio Salvador

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=1330613948.31767.12.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@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