On Thu, Jul 19, 2018 at 7:20 PM Khem Raj wrote:
>
>
> On Thu, Jul 19, 2018 at 10:26 AM Alex Kiernan wrote:
> >
> > On Thu, Jul 19, 2018 at 6:21 PM Khem Raj wrote:
> > >
> > >
> > >
> > > On 7/19/18 10:12 AM, Alex Kiernan wrote:
> > > > To handle the case where ${COREBASE} isn't the git directory
On Thu, Jul 19, 2018 at 10:26 AM Alex Kiernan
wrote:
>
> On Thu, Jul 19, 2018 at 6:21 PM Khem Raj wrote:
> >
> >
> >
> > On 7/19/18 10:12 AM, Alex Kiernan wrote:
> > > To handle the case where ${COREBASE} isn't the git directory, but
> > > ${COREBASE}/meta might be (since that's the layer that se
On Thu, Jul 19, 2018 at 6:21 PM Khem Raj wrote:
>
>
>
> On 7/19/18 10:12 AM, Alex Kiernan wrote:
> > To handle the case where ${COREBASE} isn't the git directory, but
> > ${COREBASE}/meta might be (since that's the layer that sets up the COREBASE
> > variable), use the timestamp from there. If tha
On 7/19/18 10:12 AM, Alex Kiernan wrote:
To handle the case where ${COREBASE} isn't the git directory, but
${COREBASE}/meta might be (since that's the layer that sets up the COREBASE
variable), use the timestamp from there. If that fails use the timestamp
from conf/bitbake.conf.
whats the ch
To handle the case where ${COREBASE} isn't the git directory, but
${COREBASE}/meta might be (since that's the layer that sets up the COREBASE
variable), use the timestamp from there. If that fails use the timestamp
from conf/bitbake.conf.
Signed-off-by: Alex Kiernan
---
meta/classes/image.bbcla
