Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

linux-firmware-rpidistro: set branch to buster #951

Conversation

tewarid
Copy link
Contributor

@tewarid tewarid commented Nov 19, 2021

Branch has been renamed to buster in source repo.

Also setting protocol to https as GitHub is migrating
away from unencrypted git protocol

@agherzan-ci
Copy link

Can one of the admins verify this patch?

@agherzan
Copy link
Owner

@agherzan-ci ok to test

@dosena
Copy link

dosena commented Nov 19, 2021

Could this also be added to the dunfell branch?

@shr-project
Copy link
Contributor

shr-project commented Nov 19, 2021

Could this also be added to the dunfell branch?

it's already there, see #948 it would be nice to use the same commit at least for hardknott and dunfell, so that there aren't 3 versions of the same change (honister and master have also the firmware update on top of this which is reasonable, but for hardknott and dunfell the identical commit would be better).

Master branch has been renamed to buster.
This change is dunfell-specific because master follows bullseye which
diverted from ex-master quite a lot.

Related: RPi-Distro/firmware-nonfree#20
Signed-off-by: Pavel Zhukov <[email protected]>
Signed-off-by: Devendra Tewari <[email protected]>
@tewarid tewarid force-pushed the linux-firmware-rpidistro-srcuri-branch-parameter branch from 7a70044 to 4231976 Compare November 19, 2021 14:09
@agherzan agherzan merged commit 0dc08f9 into agherzan:hardknott Nov 20, 2021
@tewarid tewarid deleted the linux-firmware-rpidistro-srcuri-branch-parameter branch November 20, 2021 10:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants