All of lore.kernel.org
 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 v2 0/2] Fix /etc/timestamp handling
Date: Thu, 01 Mar 2012 23:15:46 +0000	[thread overview]
Message-ID: <1330643746.14819.3.camel@ted> (raw)
In-Reply-To: <1330623698-25148-1-git-send-email-gary@mlbassoc.com>

On Thu, 2012-03-01 at 10:41 -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
>   e32e236 busybox: Enable 64 bit shell tests, and disable non-standard date format interpretation.
> 
> However, this format of the timestamp is not directly compatible with
> the 'date' command line, so it must be reformatted for use.  Also,
> the busybox CONFIG_FEATURE_DATE_COMPAT needs to be enabled so that all 
> versions of 'date', whether from busybox or coreutils, agree on the format 
> when setting the date from the command line.
> 
> Gary Thomas (2):
>   initscripts: Properly format date when set from timestamp
>   busybox: Restore 'date' compatability

Merged to master, thanks.

Richard




      parent reply	other threads:[~2012-03-01 23:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-01 17:41 [PATCH v2 0/2] Fix /etc/timestamp handling Gary Thomas
2012-03-01 17:41 ` [PATCH v2 1/2] initscripts: Properly format date when set from timestamp Gary Thomas
2012-03-01 17:41 ` [PATCH v2 2/2] busybox: Restore 'date' compatability Gary Thomas
2012-03-01 23:15 ` Richard Purdie [this message]

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=1330643746.14819.3.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 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.