From: John Weber <rjohnweber@gmail.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: Linux kernel recipe override question
Date: Tue, 25 Feb 2014 09:53:04 -0600 [thread overview]
Message-ID: <530CBC60.5090500@gmail.com> (raw)
In-Reply-To: <CAP9ODKq-NtHV8NwZMOQjFzTUkXw=NDhOsqN=YaN0U0pvGLMcNQ@mail.gmail.com>
Hi Otavio,
On 2/25/14, 9:34 AM, Otavio Salvador wrote:
> Hello John,
>
> On Tue, Feb 25, 2014 at 11:52 AM, John Weber <rjohnweber@gmail.com> wrote:
>> On 2/25/14, 6:20 AM, Otavio Salvador wrote:
>> SRCBRANCH works based on experience from trial and error that I've done in
>> the past.
>> SRCREV does not work, again based on what I've tried.
>>
>> I'll shoot you a patch to make it easy to test on your end.
> It makes sense now.
>
> The SRCREV is dealt different because we can use SRCREV_FORMAT.
>
> So when we use multiple Git repositories in same fetcher we can have:
>
> SRCREV_FORMAT = "first_second"
>
> and
>
> SRC_URI = "git://...;name=first \
> git://...;name=second"
>
> and
>
> SRCREV_first = ...
> SRCREV_second = ...
OK. I think I understand this.
>
> So to handle the pn, we must to use:
>
> SRCREV_pn-<recipe>
>
> or
>
> SRCREV_<name>-pn-<recipe>
Robin Findley explained where the pn- comes in. Very handy.
>
> I hope it clarifies it now.
>
> Regards,
>
next prev parent reply other threads:[~2014-02-25 15:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-24 20:27 Linux kernel recipe override question Robin Findley
2014-02-25 3:59 ` John Weber
2014-02-25 12:20 ` Otavio Salvador
2014-02-25 14:52 ` John Weber
2014-02-25 15:34 ` Otavio Salvador
2014-02-25 15:53 ` John Weber [this message]
2014-02-25 15:57 ` Gary Thomas
2014-02-25 16:39 ` Otavio Salvador
-- strict thread matches above, loose matches on Subject: below --
2014-02-24 19:51 John Weber
2014-02-24 20:05 ` Gary Thomas
2014-02-25 12:11 ` 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=530CBC60.5090500@gmail.com \
--to=rjohnweber@gmail.com \
--cc=meta-freescale@yoctoproject.org \
--cc=otavio@ossystems.com.br \
/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.