From: Robert Yang <liezhi.yang@windriver.com>
To: Patrick Doyle <wpdster@gmail.com>,
Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: [dora] x264: Update SRCREV to match commit in upstream git repo
Date: Tue, 17 Jun 2014 23:56:58 +0800 [thread overview]
Message-ID: <53A0654A.5060606@windriver.com> (raw)
In-Reply-To: <CAF_dkJDCDGLsYFDWJgOaXZwkiRLFE8XSkLAT-Knx-eX_qbH7tA@mail.gmail.com>
On 06/17/2014 11:31 PM, Patrick Doyle wrote:
> Thanks Paul,
> I hope I didn't step on any toes with this. I'm still confused about
> what parts of the project are "Yocto" and what parts are "OE".
The oe-core is a part of yocto project, which is the meta layer in
poky.
>
> Do you have any guesses as to when this might show up in the official
> dora branch?
I've resend it oe-core, and will ping RP sooner.
@Paul,
I'm sorry, seems that I missed your email, but I still can't find it
when I searched again.
// Robert
>
> I am asking because we have a development flow here (I'm still not
> sure I'm 100% happy with it, but it's what we've got), where we mirror
> the poky repository, check out from that mirror very occasionally, and
> generate a complete-from-scratch even more occasionally.
> Unfortunately, we have a situation right now where, if somebody were
> to do that (say, hypothetically speaking, a new person joins the
> team), we can't generate a complete build from scratch. I could apply
> my patch to our local mirror, and thus break the mirror. Or I could
> create a local clone of the mirror and reference our local clone. Or
> …
>
> If this will show up in dora in a matter of hours to a day or so, I'm
> going to stop thinking about this. If it is anticipated that it will
> take longer, then I'll come up with a solution.
>
> I'm not trying to complain nor advocate that this patch get applied
> faster than would be normal, I'm just trying to plan my day :-)
>
> --wpd
>
>
> On Tue, Jun 17, 2014 at 11:07 AM, Paul Eggleton
> <paul.eggleton@linux.intel.com> wrote:
>> Hi Patrick,
>>
>> On Tuesday 17 June 2014 09:36:05 Patrick Doyle wrote:
>>> It seems that 585324fee380109acd9986388f857f413a60b896 is no
>>> longer there in git and it has been rewritten to
>>> ffc3ad4945da69f3caa2b40e4eed715a9a8d9526
>>
>> FYI I sent a similar patch for dora to the OE-Core list a week ago; hopefully
>> it should be merged soon.
>>
>> (Robert: I think my CC of the patch to you at the time bounced, not sure what
>> happened.)
>>
>> Cheers,
>> Paul
>>
>> --
>>
>> Paul Eggleton
>> Intel Open Source Technology Centre
>
>
next prev parent reply other threads:[~2014-06-17 15:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-17 13:36 [dora] x264: Update SRCREV to match commit in upstream git repo Patrick Doyle
2014-06-17 15:07 ` Paul Eggleton
2014-06-17 15:31 ` Patrick Doyle
2014-06-17 15:56 ` Robert Yang [this message]
2014-06-17 16:33 ` Paul Eggleton
2014-06-17 16:46 ` Paul Eggleton
2014-06-17 17:33 ` Patrick Doyle
2014-06-17 15:41 ` How to copy recipe and have different target names Brian Smucker
2014-06-17 16:31 ` Andrea Adami
2014-06-17 16:42 ` Brian Smucker
2014-06-17 20:11 ` Brian Smucker
2014-06-18 8:25 ` Andrea Adami
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=53A0654A.5060606@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=paul.eggleton@linux.intel.com \
--cc=wpdster@gmail.com \
--cc=yocto@yoctoproject.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.