Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions default.xml
Original file line number Diff line number Diff line change
@@ -1,13 +1,13 @@
<?xml version="1.0" encoding="UTF-8" ?>
<manifest>
<remote fetch="https://github.com/nxp-auto-linux" name="alb"/>
<remote fetch="https://github.com/consider-it/meta-alb" name="alb"/>

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We might not even need this change as all forks share all commits at GitHub. But don't know what the repo tool does exactly.

E.g. you can clone https://github.com/nxp-auto-linux/meta-alb, do git fetch 981d365b4385d5b72502a9035cb26282a926deed (revision listed below) and git reset --hard to it.

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i just made this change to be coherant with what we did (witout taking into account that the work will be sent to bitbucket server)

So yes as you got point, but once the meta-alb commits are merged by NXP in their server.

<remote fetch="https://git.yoctoproject.org/git" name="yocto"/>
<remote fetch="https://git.openembedded.org" name="oe"/>

<remote fetch="https://github.com/nxp-qoriq" name="qoriq"/>

<!-- The default revision and remote are applicable to the meta-alb layer -->
<default sync-j="2" revision="3d9b44b8ef908c9745db191b6e8657f7ef36fa12" remote="alb"/>
<default sync-j="2" revision="981d365b4385d5b72502a9035cb26282a926deed" remote="alb"/>

<project name="meta-alb" path="sources/meta-alb">
<copyfile dest="nxp-setup-alb.sh" src="nxp-setup-alb.sh"/>
Expand Down