From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/1] Bugfix in PRINC increment
Date: Tue, 17 May 2011 11:25:11 -0700 [thread overview]
Message-ID: <4DD2BD87.2080307@linux.intel.com> (raw)
In-Reply-To: <cover.1305570339.git.raj.khem@gmail.com>
On 05/16/2011 11:26 AM, Khem Raj wrote:
>
> Pull URL: git://git.openembedded.org/openembedded-core-contrib
> Branch: kraj/princ
> Browse: http://git.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=kraj/princ
>
> Thanks,
> Khem Raj<raj.khem@gmail.com>
> ---
>
>
> Khem Raj (1):
> base.bbclass: Fix PR increment bug when PR number is a single digit
>
> meta/classes/base.bbclass | 19 ++++++-------------
> 1 files changed, 6 insertions(+), 13 deletions(-)
>
Merged into oe-core
Thanks
Sau!
prev parent reply other threads:[~2011-05-17 18:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-16 18:26 [PATCH 0/1] Bugfix in PRINC increment Khem Raj
2011-05-16 18:26 ` [PATCH 1/1] base.bbclass: Fix PR increment bug when PR number is a single digit Khem Raj
2011-05-17 18:25 ` Saul Wold [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=4DD2BD87.2080307@linux.intel.com \
--to=sgw@linux.intel.com \
--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