From: Joshua Lock <josh@linux.intel.com>
To: Richard Purdie <rpurdie@linux.intel.com>
Cc: yocto <yocto@yoctoproject.org>
Subject: Re: Last minute changes - Review Request
Date: Fri, 22 Oct 2010 18:16:33 +0100 [thread overview]
Message-ID: <1287767793.2483.23.camel@scimitar> (raw)
In-Reply-To: <1287757431.16386.768.camel@rex>
On Fri, 2010-10-22 at 15:23 +0100, Richard Purdie wrote:
>
> I'm not happy about being in this position and I know Dave will be very
> nervous about these late changes. To mitigate this I'd like to propose
> that a selection of people (Josh, Mark, Saul?) review these changes and
> report back on whether they feel these are appropriate and also give the
> build some testing with these applied.
I've looked over the changes and spent this afternoon testing them, I
believe they are appropriate for the 0.9 release.
Cheers,
Joshua
--
Joshua Lock
Intel Open Source Technology Centre
prev parent reply other threads:[~2010-10-22 17:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-22 14:23 Last minute changes - Review Request Richard Purdie
2010-10-22 16:32 ` Stewart, David C
2010-10-22 17:23 ` Saul G. Wold
2010-10-22 17:24 ` Mark Hatle
2010-10-22 17:48 ` Dirk Hohndel
2010-10-22 22:28 ` Stewart, David C
2010-10-22 17:16 ` Joshua Lock [this message]
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=1287767793.2483.23.camel@scimitar \
--to=josh@linux.intel.com \
--cc=rpurdie@linux.intel.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.