Openembedded Core Discussions
 help / color / mirror / Atom feed
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/2] Upstream-status --> Upstream-Status and a fix to send-pull-request
Date: Thu, 02 Jun 2011 14:51:15 +0100	[thread overview]
Message-ID: <1307022675.27470.542.camel@rex> (raw)
In-Reply-To: <cover.1307002336.git.dexuan.cui@intel.com>

On Thu, 2011-06-02 at 16:17 +0800, Dexuan Cui wrote:
> Upstream-status --> Upstream-Status:
> As a keyword, it's case sensitive, so let's fix the lowercase s here.
> 
> The fix to send-pull-request:
> I don't know why othes doesn't complain about this, but without this patch,
> the script can't run properly in my side.
> 
> 
> Thanks,
> -- Dexuan
> 
> The following changes since commit 484c4e73245c93a08413cd204513bf5c5698b994:
> 
>   clutter-1.6: Add patch to update gettext macro version (2011-06-01 18:34:37 +0100)
> 
> are available in the git repository at:
>   git://git.pokylinux.org/poky-contrib dcui/master
>   http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=dcui/master
> 
> Dexuan Cui (2):
>   recipes: Upstream-status --> Upstream-Status: for multiple patches
>   send-pull-request: fix a small typo that fails the script

Merged to master, thanks.

Richard




      parent reply	other threads:[~2011-06-02 13:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-02  8:17 [PATCH 0/2] Upstream-status --> Upstream-Status and a fix to send-pull-request Dexuan Cui
2011-06-02  8:17 ` [PATCH 1/2] recipes: Upstream-status --> Upstream-Status: for multiple patches Dexuan Cui
2011-06-02  8:17 ` [PATCH 2/2] send-pull-request: fix a small typo that fails the script Dexuan Cui
2011-06-02 13:51 ` 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=1307022675.27470.542.camel@rex \
    --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