From: Philip Balister <philip@balister.org>
To: openembedded-devel@lists.openembedded.org
Cc: Koen Kooi <k.kooi@student.utwente.nl>
Subject: Re: Request for branch merge
Date: Thu, 01 Apr 2010 17:27:51 -0400 [thread overview]
Message-ID: <4BB50FD7.8010207@balister.org> (raw)
In-Reply-To: <hp3209$de1$1@dough.gmane.org>
On 04/01/2010 05:08 PM, Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 01-04-10 22:34, Tom Rini wrote:
>> On Thu, 2010-04-01 at 13:03 -0700, Chris Larson wrote:
>>> On Thu, Apr 1, 2010 at 10:55 AM, Koen Kooi<k.kooi@student.utwente.nl>wrote:
>>>
>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>> Hash: SHA1
>>>>
>>>> On 01-04-10 17:33, Richard Purdie wrote:
>>>>
>>>>> I could post the patches individually and get Acked lines for each one
>>>>> but I'm hoping to avoid that and get permission to merge the branch
>>>>> directly. We have talked about most of these things in one form or
>>>>> another.
>>>>
>>>> I don't think this will get serious review people other than Tom, Khem
>>>> and Chris, so if they don't have huge objections, merge it and we'll
>>>> deal with the fallout together if needed.
>>>
>>>
>>> I agree with Koen on this, it's a definite improvement. Let's get it merged
>>> and deal with any fallout from there.
>>
>> Generally yes, and just a few things to hash out over the weekend I
>> think.
>
> I'm going to steal Chris' thunder a bit, but during the TSC meeting we
> agreed that "after the weekend" would be a better time to merge it than
> "now". Dealing with the fallout required lots of attention, which boils
> down to "office hours" for most of the involved.
Thanks. I know the people who do work on OE over the weekends appreciate
this.
Philip
next prev parent reply other threads:[~2010-04-01 21:31 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 15:33 Request for branch merge Richard Purdie
2010-04-01 15:41 ` Tom Rini
2010-04-01 15:43 ` Tom Rini
2010-04-01 16:07 ` Richard Purdie
2010-04-01 16:45 ` Tom Rini
2010-04-01 18:09 ` Richard Purdie
2010-04-01 18:33 ` Tom Rini
2010-04-01 18:43 ` Richard Purdie
2010-04-01 16:05 ` Richard Purdie
2010-04-01 16:46 ` Tom Rini
2010-04-01 15:46 ` Khem Raj
2010-04-01 16:09 ` Richard Purdie
2010-04-01 16:18 ` Andrea Adami
2010-04-01 16:29 ` Richard Purdie
2010-04-01 16:37 ` Gary Thomas
2010-04-01 17:17 ` Joshua Lock
2010-04-01 17:55 ` Koen Kooi
2010-04-01 18:17 ` Richard Purdie
2010-04-01 20:03 ` Chris Larson
2010-04-01 20:34 ` Tom Rini
2010-04-01 21:08 ` Koen Kooi
2010-04-01 21:25 ` Tom Rini
2010-04-01 21:27 ` Philip Balister [this message]
2010-04-01 22:26 ` Tom Rini
2010-04-02 13:40 ` Koen Kooi
2010-04-02 14:35 ` Koen Kooi
2010-04-02 21:41 ` Richard Purdie
2010-04-03 7:21 ` Koen Kooi
2010-04-02 21:29 ` Richard Purdie
2010-04-03 7:23 ` Koen Kooi
2010-04-08 15:40 ` Joshua Lock
2010-04-03 13:24 ` Koen Kooi
2010-04-12 8:37 ` Koen Kooi
2010-04-12 15:59 ` Tom Rini
2010-04-12 16:46 ` Joshua Lock
2010-05-01 23:29 ` Richard Purdie
2010-05-03 16:46 ` Tom Rini
2010-05-04 18:10 ` Richard Purdie
2010-05-04 18:55 ` Tom Rini
2010-05-05 23:22 ` Richard Purdie
2010-05-05 23:30 ` Tom Rini
2010-04-12 16:45 ` Joshua Lock
2010-04-12 17:47 ` Koen Kooi
2010-04-12 20:55 ` Koen Kooi
2010-04-12 22:19 ` Koen Kooi
2010-04-13 3:46 ` Richard Purdie
2010-04-13 7:06 ` Koen Kooi
2010-05-01 23:28 ` Richard Purdie
2010-05-02 14:13 ` Koen Kooi
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=4BB50FD7.8010207@balister.org \
--to=philip@balister.org \
--cc=k.kooi@student.utwente.nl \
--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