All of lore.kernel.org
 help / color / mirror / Atom feed
From: Otavio Salvador <otavio@ossystems.com.br>
To: openembedded-devel@lists.openembedded.org
Subject: [meta-oe][PATCH 0/2] Move connman to oe-core and fix dropbear PR
Date: Sat, 10 Dec 2011 16:33:54 +0000	[thread overview]
Message-ID: <cover.1323534795.git.otavio@ossystems.com.br> (raw)

The following changes since commit 70cd3a81edb9fd2aba149db243e53934930e0d85:

  libgnome-keyring 2.32.0: fix LICENSE operand (2011-12-10 14:43:54 +0100)

are available in the git repository at:
  git://github.com/OSSystems/meta-oe master
  https://github.com/OSSystems/meta-oe/tree/master

Otavio Salvador (2):
  connman: convert to bbappend as 0.78 has been moved to OE-Core
  dropbear: convert PR to use PRINC on bbappend

 meta-oe/recipes-connectivity/connman/connman.inc   |   98 --------------------
 .../recipes-connectivity/connman/connman/connman   |   42 ---------
 .../recipes-connectivity/connman/connman_0.78.bb   |   33 -------
 .../connman/connman_0.78.bbappend                  |   13 +++
 .../dropbear/dropbear_2011.54.bbappend             |    2 +-
 5 files changed, 14 insertions(+), 174 deletions(-)
 delete mode 100644 meta-oe/recipes-connectivity/connman/connman.inc
 delete mode 100755 meta-oe/recipes-connectivity/connman/connman/connman
 delete mode 100644 meta-oe/recipes-connectivity/connman/connman_0.78.bb
 create mode 100644 meta-oe/recipes-connectivity/connman/connman_0.78.bbappend

-- 
1.7.2.5




             reply	other threads:[~2011-12-10 16:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-10 16:33 Otavio Salvador [this message]
2011-12-10 16:33 ` [meta-oe][PATCH 1/2] connman: convert to bbappend as 0.78 has been moved to OE-Core Otavio Salvador
2011-12-10 16:33 ` [meta-oe][PATCH 2/2] dropbear: convert PR to use PRINC on bbappend Otavio Salvador

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.1323534795.git.otavio@ossystems.com.br \
    --to=otavio@ossystems.com.br \
    --cc=openembedded-devel@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.