From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Saul Wold <sgw@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [Consolidated Pull 00/33] Fixes and Updates
Date: Mon, 03 Dec 2012 14:14:47 +0000 [thread overview]
Message-ID: <1354544087.5970.11.camel@ted> (raw)
In-Reply-To: <cover.1354263334.git.sgw@linux.intel.com>
On Fri, 2012-11-30 at 00:17 -0800, Saul Wold wrote:
> Richard,
>
> This is a combo request with your master-next and MUT,
> it builds with AutoBuild and I have done some simple
> testing.
>
> I have droped some patches that do not have Upstream-Status
> info.
>
> Thanks
> Sau!
>
>
>
> The following changes since commit 99f003356be43bb361634359a5d3c520f72f0a08:
>
> local.conf.sample: Enable disk space monitoring by default (2012-11-28 15:25:14 +0000)
>
> are available in the git repository at:
>
> git://git.openembedded.org/openembedded-core-contrib sgw/updates
> http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=sgw/updates
This branch doesn't contain the things this email says it should :/
Cheers,
Richard
prev parent reply other threads:[~2012-12-03 14:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-30 8:17 [Consolidated Pull 00/33] Fixes and Updates Saul Wold
2012-12-03 14:14 ` Richard Purdie [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=1354544087.5970.11.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=sgw@linux.intel.com \
/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.