-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Pay down technical debt #1884
Comments
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
For now, let's hold off from sending more patches upstream, as we are in the code freeze period leading up to Git v2.20.0. |
|
|
|
|
|
|
I added GitGitGadget PRs for all of the branches in |
This is a meta work item, really: I spent some two days last week to perform a merging-rebase of our
master
onto itself, with the sole purpose of reordering patches/patch series into a shape that allows us to know exactly where we are with the patches. One outcome is theready-for-upstream
branch thicket, combining all of the patch series I deem ready for upstream. Here is the check list (the idea being to check every patch series as it is chomped off the list):The text was updated successfully, but these errors were encountered: