From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] turning conf/machine into a set of bblayers
Date: Mon, 01 Nov 2010 14:04:40 -0700 [thread overview]
Message-ID: <4CCF2B68.2070201@mentor.com> (raw)
In-Reply-To: <AANLkTi=74mwvxLLwCjEhV3OMCyOdpfRZeU0Z-bf6TM+P@mail.gmail.com>
Frans Meulenbroeks wrote:
> 2010/10/21 Graeme Gregory <dp@xora.org.uk>:
>
>> Such a pity git doesnt have increasing rev numbers, a cool adition would
>> be a flag in layer that showed the last rev of core it was tested with.
>>
>> Layer was tested with core 1 but core is now 999 would give an
>> indication on drift between layers and core.
>>
>> Graeme
>
> Triggered by this (and apologies if I am drifting off-topic).
> It would be nice if with amend.inc you could specify the PR of the
> underlying recipe that this amend is for (and get a warning or error
> if there is a mismatch)
I know I'm late to the party but.. I don't think this is a big deal.
Changes getting out of sync from foopkg 1.1 to foopkg 1.2? Yes. foopkg
1.1 PR="r1" to 1.1 PR="r10" ? Unlikely and something the human control
side should be able to handle.
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2010-11-01 22:34 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-21 9:33 [RFC] turning conf/machine into a set of bblayers Koen Kooi
2010-10-21 9:52 ` Graeme Gregory
2010-10-21 9:59 ` Koen Kooi
2010-10-21 10:04 ` Graeme Gregory
2010-10-21 10:17 ` Frans Meulenbroeks
2010-10-21 10:20 ` Frans Meulenbroeks
2010-10-21 10:38 ` Richard Purdie
2010-10-21 12:01 ` Frans Meulenbroeks
2010-10-21 13:46 ` Maupin, Chase
2010-10-21 14:21 ` Chris Larson
2010-10-21 16:11 ` Denys Dmytriyenko
2010-11-01 21:04 ` Tom Rini [this message]
2010-10-21 10:48 ` Richard Purdie
2010-10-21 11:22 ` Graeme Gregory
2010-10-21 14:21 ` Chris Larson
2010-10-21 10:36 ` Richard Purdie
2010-11-02 7:02 ` Frans Meulenbroeks
2010-11-02 20:46 ` Koen Kooi
2010-11-02 21:14 ` Eric Bénard
2010-11-02 21:19 ` Koen Kooi
2010-11-02 21:21 ` Tom Rini
2010-11-03 8:15 ` Frans Meulenbroeks
2010-11-03 14:59 ` Tom Rini
2010-11-03 18:59 ` Frans Meulenbroeks
2010-11-03 20:17 ` Tom Rini
2010-11-03 20:44 ` Khem Raj
2010-11-03 21:06 ` Frans Meulenbroeks
2010-11-03 22:13 ` Khem Raj
2010-11-04 7:48 ` Koen Kooi
2010-11-02 21:57 ` Khem Raj
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=4CCF2B68.2070201@mentor.com \
--to=tom_rini@mentor.com \
--cc=openembedded-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