Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Otavio Salvador <otavio@ossystems.com.br>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/3] Pending O.S. Systems' tree patches
Date: Fri, 17 Feb 2012 17:47:02 +0000	[thread overview]
Message-ID: <cover.1329500798.git.otavio@ossystems.com.br> (raw)

The following changes since commit e5ad03093dfc4364d1407183f458df79f347c7a1:

  guile: fix cross configure failure (2012-02-10 13:38:16 +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):
  update-rc.d.bbclass: do nothing for extended cross packages
  rootfs_ipk.bbclass: fix status file location in rootfs
  rootfs_ipk.bbclass: fix unpacked postinst support if no package
    management

 meta/classes/rootfs_ipk.bbclass  |   21 ++++++++++++++++++---
 meta/classes/update-rc.d.bbclass |    1 +
 2 files changed, 19 insertions(+), 3 deletions(-)

-- 
1.7.2.5




             reply	other threads:[~2012-02-17 17:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-17 17:47 Otavio Salvador [this message]
2012-02-17 17:47 ` [PATCH 1/3] update-rc.d.bbclass: do nothing for extended cross packages Otavio Salvador
2012-02-17 17:47 ` [PATCH 2/3] rootfs_ipk.bbclass: fix status file location in rootfs Otavio Salvador
2012-02-17 17:47 ` [PATCH 3/3] rootfs_ipk.bbclass: fix unpacked postinst support if no package management Otavio Salvador
2012-02-17 17:51   ` Phil Blundell
2012-02-17 19:06     ` Otavio Salvador
2012-02-17 19:25       ` Phil Blundell
2012-02-17 19:30         ` Otavio Salvador
2012-02-17 19:59           ` Phil Blundell
2012-02-17 20:03             ` Otavio Salvador
2012-02-17 20:11               ` Phil Blundell
2012-02-17 20:14                 ` Otavio Salvador
2012-02-17 20:29                   ` Phil Blundell
2012-02-18  3:56                     ` Otavio Salvador
2012-02-24  4:06 ` [PATCH 0/3] Pending O.S. Systems' tree patches Saul Wold

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=cover.1329500798.git.otavio@ossystems.com.br \
    --to=otavio@ossystems.com.br \
    --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