From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Cc: Darren Hart <dvhart@linux.intel.com>
Subject: Re: [PATCH 0/1] kernel: move menuconfig task after configure
Date: Fri, 01 Jul 2011 00:18:01 +0100 [thread overview]
Message-ID: <1309475881.20015.497.camel@rex> (raw)
In-Reply-To: <cover.1309380310.git.dvhart@linux.intel.com>
On Wed, 2011-06-29 at 13:46 -0700, Darren Hart wrote:
> The following changes since commit e0fc42b51a8209dac1163ae8126f8c687b6bfddf:
>
> distro_tracking_fields.inc: update RECIPE_MANUAL_CHECK_DATE for screen and tcf-agent (2011-06-29 15:04:59 +0100)
>
> are available in the git repository at:
> git://git.pokylinux.org/poky-contrib dvhart/kernel
> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=dvhart/kernel
>
> Darren Hart (1):
> kernel: move menuconfig task after configure
Merged to master, thanks.
Richard
prev parent reply other threads:[~2011-06-30 23:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-29 20:46 [PATCH 0/1] kernel: move menuconfig task after configure Darren Hart
2011-06-29 20:46 ` [PATCH 1/1] " Darren Hart
2011-06-30 23:18 ` 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=1309475881.20015.497.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=dvhart@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox