meta-labgrid: use scarthgap branch instead of master #149
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The tip of the master branch is no longer compatible with the scarthgap release, since it has the UNPACKDIR changes that are required for styhead. Since the scarthgap branch exists now and is up to date (it didn't initially, which is why this was set to "master") use that now. Signed-off-by: Leonard Göhrs <l.goehrs@pengutronix.de>
hnez
force-pushed
the
meta-labgrid-scarthgap
branch
from
e4c48ea to
2e32c9d
Compare
jluebbe
approved these changes
Jul 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The tip of the master branch is no longer compatible with the scarthgap release, since it has the UNPACKDIR changes that are required for styhead. Since the scarthgap branch exists now and is up to date (it didn't initially, which is why this was set to "master") use that now.
This should solve the issue encountered by dependabot in #148.