Multi-line f-string for vs code configuration file contents#98
Open
paulober wants to merge 1 commit intoraspberrypi:masterfrom
Open
Multi-line f-string for vs code configuration file contents#98paulober wants to merge 1 commit intoraspberrypi:masterfrom
paulober wants to merge 1 commit intoraspberrypi:masterfrom
Conversation
Contributor
|
As James mentioned in another issue, he's gone on holiday so you won't get a reply for a while... 😎 |
Contributor
Author
|
Oh right, I had forgotten about that. |
Contributor
|
I am back, but quite busy at the moment. Will try and get some time to look at this. |
Contributor
I wonder why? 😉 https://www.raspberrypi.com/news/introducing-raspberry-pi-5/ |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
@JamesH65 I recreated the multi-line f-string because there have been some changes in the master branch that would make merging from the update branch into the master branch a mess.
So I thought about the following change: how about resetting the Windows update branch to master (aka main) and re-populating the changes needed for better Windows compatibility from your 2ab988c commit along with the PRs I added to it.
And then redirect all new PRs to that development branch until it is merged?