Replies: 1 comment
-
One way could be to make the PR against 4.0 and later when the 4.1-dev branch has been updated to 4.0-dev so the changes mentioned above went up to 4.1-dev, what should happen one day, rebase the PR to 4.1-dev. Another way could be to contact @bembelimen and check with him what's the best way. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Example: I have implemented something in branch 4.0 because it builds on things that are not yet integrated in 4.1. If I set the PR against branch 4.1, I cannot see what I have changed because many things are missing and therfore are many differnces.
#32969 and #32968
Beta Was this translation helpful? Give feedback.
All reactions