Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: <jackie.huang@windriver.com>
To: <openembedded-devel@lists.openembedded.org>
Subject: [meta-networking][PATCH 0/1] waf-samba.bbclass: move to meta-networking
Date: Thu, 10 Mar 2016 14:33:09 +0800	[thread overview]
Message-ID: <cover.1457591235.git.jackie.huang@windriver.com> (raw)

From: Jackie Huang <jackie.huang@windriver.com>

This is a follow-up from the discussion in the thread:
"Re: [oe] Still many meta-networking changes waiting in patchwork/master-next"

--
The following changes since commit a1e135a499998add7575682bf53db5e02e753580:

  Revert "toybox: upgrade to 0.7.0" (2016-03-07 13:02:19 +0100)

are available in the git repository at:

  git://git.pokylinux.org/poky-contrib.git jhuang0/t_move-waf-samba_160310-0
  http://git.pokylinux.org/cgit.cgi//log/?h=jhuang0/t_move-waf-samba_160310-0

Jackie Huang (1):
  waf-samba.bbclass: move to meta-networking

 {meta-oe => meta-networking}/classes/waf-samba.bbclass                 | 0
 meta-networking/conf/layer.conf                                        | 3 +++
 {meta-oe => meta-networking}/files/waf-cross-answers/README            | 0
 .../files/waf-cross-answers/cross-answers-aarch64.txt                  | 0
 .../files/waf-cross-answers/cross-answers-arm.txt                      | 0
 .../files/waf-cross-answers/cross-answers-i586.txt                     | 0
 .../files/waf-cross-answers/cross-answers-i686.txt                     | 0
 .../files/waf-cross-answers/cross-answers-mips.txt                     | 0
 .../files/waf-cross-answers/cross-answers-mips64.txt                   | 0
 .../files/waf-cross-answers/cross-answers-powerpc.txt                  | 0
 .../files/waf-cross-answers/cross-answers-powerpc64.txt                | 0
 .../files/waf-cross-answers/cross-answers-x86_64.txt                   | 0
 meta-oe/conf/layer.conf                                                | 1 -
 13 files changed, 3 insertions(+), 1 deletion(-)
 rename {meta-oe => meta-networking}/classes/waf-samba.bbclass (100%)
 rename {meta-oe => meta-networking}/files/waf-cross-answers/README (100%)
 rename {meta-oe => meta-networking}/files/waf-cross-answers/cross-answers-aarch64.txt (100%)
 rename {meta-oe => meta-networking}/files/waf-cross-answers/cross-answers-arm.txt (100%)
 rename {meta-oe => meta-networking}/files/waf-cross-answers/cross-answers-i586.txt (100%)
 rename {meta-oe => meta-networking}/files/waf-cross-answers/cross-answers-i686.txt (100%)
 rename {meta-oe => meta-networking}/files/waf-cross-answers/cross-answers-mips.txt (100%)
 rename {meta-oe => meta-networking}/files/waf-cross-answers/cross-answers-mips64.txt (100%)
 rename {meta-oe => meta-networking}/files/waf-cross-answers/cross-answers-powerpc.txt (100%)
 rename {meta-oe => meta-networking}/files/waf-cross-answers/cross-answers-powerpc64.txt (100%)
 rename {meta-oe => meta-networking}/files/waf-cross-answers/cross-answers-x86_64.txt (100%)

-- 
1.9.1



             reply	other threads:[~2016-03-10  6:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-10  6:33 jackie.huang [this message]
2016-03-10  6:33 ` [meta-networking][PATCH 1/1] waf-samba.bbclass: move to meta-networking jackie.huang

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.1457591235.git.jackie.huang@windriver.com \
    --to=jackie.huang@windriver.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox