All of lore.kernel.org
 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/3] Pending patches from O.S. Systems' tree
Date: Wed, 29 Feb 2012 13:00:02 +0000	[thread overview]
Message-ID: <1330520402.24508.40.camel@ted> (raw)
In-Reply-To: <cover.1330494042.git.otavio@ossystems.com.br>

On Wed, 2012-02-29 at 05:41 +0000, Otavio Salvador wrote:
> The following changes since commit 61216d2743502ef38955054aad6a4f2ed63e6d43:
> 
>   licenses.conf: fix quotting of SRC_DISTRIBUTE_LICENSES (2012-02-28 17:51:42 +0000)
> 
> are available in the git repository at:
>   git://github.com/OSSystems/oe-core master
>   https://github.com/OSSystems/oe-core/tree/HEAD
> 
> Otavio Salvador (3):
>   image.bbclass: do not create image manifest link if IMAGE_LINK_NAME
>     is empty
>   image_types.bbclass: properly support IMAGE_LINK_NAME as empty
>   image_types.bbclass: fix bzip2 and xz compression commands

Merged to master, thanks (with one tweak I've mentioned).

Cheers,

Richard




      parent reply	other threads:[~2012-02-29 13:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-29  5:41 [PATCH 0/3] Pending patches from O.S. Systems' tree Otavio Salvador
2012-02-29  5:41 ` [PATCH 1/3] image.bbclass: do not create image manifest link if IMAGE_LINK_NAME is empty Otavio Salvador
2012-02-29  5:41 ` [PATCH 2/3] image_types.bbclass: properly support IMAGE_LINK_NAME as empty Otavio Salvador
2012-02-29 12:56   ` Richard Purdie
2012-02-29  5:41 ` [PATCH 3/3] image_types.bbclass: fix bzip2 and xz compression commands Otavio Salvador
2012-02-29 13:00 ` 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=1330520402.24508.40.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.