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/1] mktemp: mark patch as upstreamed
Date: Mon, 19 Dec 2011 12:16:09 +0000 [thread overview]
Message-ID: <1324296969.4568.162.camel@ted> (raw)
In-Reply-To: <cover.1324251354.git.scott.a.garman@intel.com>
On Sun, 2011-12-18 at 15:37 -0800, Scott Garman wrote:
> Hello,
>
> I submitted a parallel make patch upstream to the mktemp maintainer,
> who has accepted it. This just updates our patch's Upstream-Status
> field accordingly.
>
> Scot
>
>
> The following changes since commit 3e05acab1c119a3b2a4703ea8729cc768935d36e:
>
> license.bbclass: remove bashism (2011-12-16 16:50:39 +0000)
>
> are available in the git repository at:
> git://git.pokylinux.org/poky-contrib sgarman/upstreamed
> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=sgarman/upstreamed
>
> Scott Garman (1):
> mktemp: mark patch as upstreamed
Merged to master, thanks.
Richard
prev parent reply other threads:[~2011-12-19 12:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-18 23:37 [PATCH 0/1] mktemp: mark patch as upstreamed Scott Garman
2011-12-18 23:37 ` [PATCH 1/1] " Scott Garman
2011-12-19 12:16 ` 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=1324296969.4568.162.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.