[fsl-community-bsp-platform] use master-next meta-fsl-ppc for master-next manifest

Submitted by Bob Cochran on Aug. 8, 2014, 3:33 p.m. | Patch ID: 77553


Message ID 1407512020-11502-1-git-send-email-yocto@mindchasers.com
State Accepted, archived
Delegated to: Otavio Salvador
Headers show

Commit Message

Bob Cochran Aug. 8, 2014, 3:33 p.m.
Both master and master-next branches exist for meta-fsl-ppc, so use
the meta-fsl-ppc master-next branch in the manifest file on its
master-next branch.

Change-Id: I4e4a8455b4bcea2195159d8c2ae0b5188606c1ed

Signed-off-by: Bob Cochran <yocto@mindchasers.com>
 default.xml |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Patch hide | download patch | download mbox

diff --git a/default.xml b/default.xml
index 1365111..642ba80 100644
--- a/default.xml
+++ b/default.xml
@@ -9,7 +9,7 @@ 
   <project remote="yocto" revision="master" name="poky" path="sources/poky"/>
   <project remote="yocto" revision="master-next" name="meta-fsl-arm" path="sources/meta-fsl-arm"/>
-  <project remote="yocto" revision="master" name="meta-fsl-ppc" path="sources/meta-fsl-ppc"/>
+  <project remote="yocto" revision="master-next" name="meta-fsl-ppc" path="sources/meta-fsl-ppc"/>
   <project remote="oe" revision="master" name="meta-openembedded" path="sources/meta-openembedded"/>