-
Notifications
You must be signed in to change notification settings - Fork 5
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
Please forward patches upstream #32
Comments
OK , I very busy right now , I though in squash all commits into a few , may I just can reply on end of the month . Thanks |
thx for feedback there is no emergency we can do it anytime. Meanwhile my "priority" is to release tables on current version, double check will be welcome: |
Is there any patches here worth up streaming, feel free to comment each of them on linked page and then tick the box Preferably start from top to bottom Relate-to: adoptware#15
|
I am considering to release a version soon or later |
sorry ENOTIME |
Hi, I might release a new version (on SDL2) maybe I should ping authors to port their patch to upstream: @sergiomb2 If this version is no more maintained, Same question applies pinedit , I might revive it soon or later. BTW I'll explain about pincab profile at #LGM2021 see latest news at: |
https://github.com/sergiomb2/pinball/commits/devel have all commits of SDL2 , but when pinball start it the screen wasn't refresh , we need to move or rezise windows to refresh buffer . yes this version is no more maintained, neither pinedit |
I didn't observe this behaviour on my version, anyway about tranfering pinedit let's discuss how to do it at: |
It would be appreciated if we could avoid double maintenance effort
I started to pick some of your changes,
now can you please consider to forward valuable patches
that are not merged in this branch:
https://github.com/rzr/pinball
Smaller changes are better and easier to review:
adoptware#2
Then you can try to rebase on upstream
I also plan to release a new version which number do you suggest ?
The text was updated successfully, but these errors were encountered: