From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Damian, Alexandru" <alexandru.damian@intel.com>
Cc: Paul Eggleton <paul.eggleton@linux.intel.com>,
bitbake-devel <bitbake-devel@lists.openembedded.org>,
"toaster@yoctoproject.org" <toaster@yoctoproject.org>
Subject: Re: Toaster patchset for merging
Date: Wed, 23 Jul 2014 20:08:22 +0100 [thread overview]
Message-ID: <1406142502.22985.128.camel@ted> (raw)
In-Reply-To: <CAJ2CSBuuD9Qv=YdkGmzRY3ev9zJ=cESm_-Bg8BdDTnOvkOm+dQ@mail.gmail.com>
On Wed, 2014-07-23 at 18:16 +0100, Damian, Alexandru wrote:
> Hi Richard,
>
>
> Thanks for the test push on master-next.
>
>
> I tested master-next and it works fine !
>
>
> However, on prompt from Paul, I refactored the patchset to proper
> spell out changes in the commit messages.
>
>
> Can you please pull:
>
>
> poky-contrib: adamian/20140723-master-next-refactored
>
>
> The final diff between this new branch and master-next is NIL, but the
> commit messages are updated.
>
Thanks, its merged.
Cheers,
Richard
prev parent reply other threads:[~2014-07-23 19:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-23 17:16 Toaster patchset for merging Damian, Alexandru
2014-07-23 19:08 ` 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=1406142502.22985.128.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=alexandru.damian@intel.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=paul.eggleton@linux.intel.com \
--cc=toaster@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox