From: Scott Garman <scott.a.garman@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 1/1] buildhistory: fix multiple commit of images and packages at the same time
Date: Mon, 07 May 2012 10:00:25 -0700 [thread overview]
Message-ID: <4FA7FFA9.1090001@intel.com> (raw)
In-Reply-To: <DE0A7E5C-90AF-4379-B962-DC7B6FBD1E64@dominion.thruhere.net>
On 05/07/2012 09:03 AM, Koen Kooi wrote:
>
> Op 7 mei 2012, om 17:47 heeft Scott Garman het volgende geschreven:
>
>> On 05/04/2012 11:55 PM, Koen Kooi wrote:
>>>
>>> Op 4 mei 2012, om 23:25 heeft Scott Garman het volgende geschreven:
>>>
>>>> On 05/04/2012 08:16 AM, Koen Kooi wrote:
>>>>>>>> On Friday 04 May 2012 15:50:16 Koen Kooi wrote:
>>>>>>>>> Looks good to me. If this goes in, can it go on the
>>>>>>>>> denzil shortlist as well?
>>>>>>>>
>>>>>>>> I hope so, hence I've CC'd Scott Garman who is pulling
>>>>>>>> together a branch for 1.2.1.
>>>>>>>
>>>>>>> oe-core or poky? I only care about oe-core.
>>>>>>
>>>>>> Both. Nothing goes into poky these days unless it comes from
>>>>>> one of the appropriate trees.
>>>>>
>>>>> That's not what I was asking. I was asking it scott is doing a
>>>>> poky or oe-core effort. From Scotts emails it seems like a poky
>>>>> effort.
>>>>
>>>> Hi Koen,
>>>>
>>>> I apologize for having made some confusing comments earlier about
>>>> rebasing a denzil-next branch on my poky-contrib repo from being
>>>> based on oe-core to poky. Since then, Richard has given me access
>>>> to the oe-core-contrib repo, and I am now maintaining two
>>>> denzil-next branches.
>>>>
>>>> This one is based on oe-core:
>>>>
>>>> http://git.openembedded.org/openembedded-core-contrib/log/?h=sgarman/denzil-next
>>>
>>>>
>>> When is that going to get merged into denzil? I'm in serious need of
>>> that connman tests fix, so I have been using
>>> http://cgit.openembedded.org/openembedded-core/log/?h=denzil-next
>>> locally.
>>
>> The commit just got into master, so I'm hoping to pull it into my denzil-next-testing branch and run some build tests overnight tonight, then merge it if all goes well tomorrow.
>
> Merge it into the oe-core 'denzil' branch, right?
No. I do not have commit access to the oe-core repository, just the
oe-core-contrib repo, where my sgarman/denzil-next branch lives.
Richard is on holiday until tomorrow, can you hold on until then and
maybe he can help clear up the remaining confusion?
Scott
--
Scott Garman
Embedded Linux Engineer - Yocto Project
Intel Open Source Technology Center
next prev parent reply other threads:[~2012-05-07 17:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 13:36 [PATCH 0/1] Buildhistory fix Paul Eggleton
2012-05-04 13:36 ` [PATCH 1/1] buildhistory: fix multiple commit of images and packages at the same time Paul Eggleton
2012-05-04 13:50 ` Koen Kooi
2012-05-04 14:30 ` Paul Eggleton
2012-05-04 15:06 ` Koen Kooi
2012-05-04 15:09 ` Paul Eggleton
2012-05-04 15:13 ` Richard Purdie
2012-05-04 15:16 ` Koen Kooi
2012-05-04 21:25 ` Scott Garman
2012-05-05 6:55 ` Koen Kooi
2012-05-07 15:47 ` Scott Garman
2012-05-07 16:03 ` Koen Kooi
2012-05-07 17:00 ` Scott Garman [this message]
2012-05-04 17:23 ` [PATCH 0/1] Buildhistory fix Saul Wold
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=4FA7FFA9.1090001@intel.com \
--to=scott.a.garman@intel.com \
--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.