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

Move garatronic_pybstick26_rp2040.h to develop branch #671

Closed
wants to merge 5 commits into from

Conversation

garatronic
Copy link
Contributor

pybstick26_rp2040.h become garatronic_pybstick26_rp2040.h

@kilograham
Copy link
Contributor

this is still an add of the new file without a remove of the old file

@garatronic
Copy link
Contributor Author

hope this will do the job...

@lurch
Copy link
Contributor

lurch commented Dec 2, 2021

Still only showing "Files changed: 1" up at the top... 😕

@garatronic
Copy link
Contributor Author

I pray on my knees

@lurch
Copy link
Contributor

lurch commented Dec 2, 2021

Ahhhh, you've based this PR on top of a 25th October version of pico-sdk (see https://github.com/garatronic/pico-sdk/commits/develop ), which was from before #636 (which added pybstick26_rp2040.h) was merged; and I think that's why the "Files changed" tab on this PR is only showing garatronic_pybstick26_rp2040.h as being added and isn't showing pybstick26_rp2040.h as being removed.

I think you need to rebase your garatronic:develop branch up to a more recent version of raspberrypi:develop ? I dunno the best way of doing that but perhaps @kilograham can advise?

@kilograham
Copy link
Contributor

e.g.

git fetch
git rebase origin/develop

@garatronic
Copy link
Contributor Author

garatronic commented Dec 3, 2021 via email

@lurch
Copy link
Contributor

lurch commented Dec 3, 2021

That looks vaguely right, but I think you want to do everything on develop and ignore the master branch ?

@garatronic
Copy link
Contributor Author

garatronic commented Dec 3, 2021 via email

@lurch
Copy link
Contributor

lurch commented Dec 3, 2021

If you delete it on develop, then that "deletion" will also happen when we next merge the develop branch into the master branch.

@kilograham
Copy link
Contributor

yeah, don't checkout master

@garatronic
Copy link
Contributor Author

So, supposing you validate the PR at it is now, it will add, on next tagged version V1.3.1, 'garatronic_pybstick26_rp2040.h' into master branch side by side with the other 'pybstick26_rp2040.h', no ?

@lurch
Copy link
Contributor

lurch commented Dec 3, 2021

Correct. But if you update this PR as instructed to delete 'pybstick26_rp2040.h' from the develop branch, then when we merge develop into master (and tag v1.3.1) then git will also delete the 'pybstick26_rp2040.h' file from the master branch too. Git is clever like that 😉

@garatronic
Copy link
Contributor Author

"Le mieux est parfois l'ennemi du bien"
I give up. Do what you want.

@lurch
Copy link
Contributor

lurch commented Dec 6, 2021

@garatronic see #675

@kilograham kilograham closed this Dec 6, 2021
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.

None yet

3 participants