From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/4] Minor fixes
Date: Thu, 05 Jan 2012 11:26:44 +0000 [thread overview]
Message-ID: <1325762804.20759.59.camel@ted> (raw)
In-Reply-To: <cover.1325755613.git.paul.eggleton@linux.intel.com>
On Thu, 2012-01-05 at 09:29 +0000, Paul Eggleton wrote:
> Fix an omitted Upstream-Status in a recent patch I added, plus some text
> changes in a few other places.
>
> The following changes since commit f309769d10cb3d8b72b8c7c4f7f418dcb8422c61:
>
> valgrind: Fix for automake update (2012-01-04 16:03:59 +0000)
>
> are available in the git repository at:
> git://git.openembedded.org/openembedded-core-contrib paule/fixes9
> http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/fixes9
>
> Paul Eggleton (4):
> classes/update-alternatives: fix typos and grammar
> README: add short description of OE-Core
> conf/local.conf.sample: fix typos/grammar/formatting
> qt4: add Upstream-Status to recently added qt-4.8.0 patch
Merged to master thanks.
Richard
next prev parent reply other threads:[~2012-01-05 11:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-05 9:29 [PATCH 0/4] Minor fixes Paul Eggleton
2012-01-05 9:29 ` [PATCH 1/4] classes/update-alternatives: fix typos and grammar Paul Eggleton
2012-01-05 9:29 ` [PATCH 2/4] README: add short description of OE-Core Paul Eggleton
2012-01-05 9:29 ` [PATCH 3/4] conf/local.conf.sample: fix typos/grammar/formatting Paul Eggleton
2012-01-05 9:29 ` [PATCH 4/4] qt4: add Upstream-Status to recently added qt-4.8.0 patch Paul Eggleton
2012-01-05 11:26 ` Richard Purdie [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-09-18 17:53 [PATCH 0/4] minor fixes kusumi.tomohiro
2017-09-18 18:04 ` Jens Axboe
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=1325762804.20759.59.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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.