From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/2] data.py: fixed message domain errors
Date: Fri, 14 Oct 2011 13:47:43 +0100 [thread overview]
Message-ID: <1318596472.2342.15.camel@ted> (raw)
In-Reply-To: <1315913433-32608-2-git-send-email-s.stirtzel@googlemail.com>
On Tue, 2011-09-13 at 13:30 +0200, Samuel Stirtzel wrote:
> The dynamic message domain was introduced by Richard Purdie with the following patch:
> http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=a6c48298b17e6a5844b3638b422fe226e3b67b89
>
> Signed-off-by: Samuel Stirtzel <s.stirtzel@googlemail.com>
> ---
> meta/lib/oe/data.py | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
Patches 1 and 2 merged to master, thanks.
Sorry about the delay.
Richard
prev parent reply other threads:[~2011-10-14 12:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-13 11:30 [PATCH 1/2] patch.py: fixed message domain errors Samuel Stirtzel
2011-09-13 11:30 ` [PATCH 2/2] data.py: " Samuel Stirtzel
2011-10-14 12:47 ` 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=1318596472.2342.15.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox