-
Notifications
You must be signed in to change notification settings - Fork 141
Deprecate git rebase -p
even more
#227
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
Conversation
The `--preserve-merges` option has been deprecated, and as a consequence we started to mark test cases that require that option to be supported, in preparation for removing that support eventually. Since we marked those test cases, a couple more crept into the test suite, and with this patch, we mark them, too. Signed-off-by: Johannes Schindelin <[email protected]>
As of Git v2.22.0, the `--preserve-merges` backend of `git rebase` will be officially deprecated in favor of the `--rebase-merges` backend. Consequently, `git pull --rebase=preserve` will also be deprected. State this explicitly. Signed-off-by: Johannes Schindelin <[email protected]>
The `--preserve-merges` option is now deprecated in favor of `--rebase-merges`; Let's stop recommending the former. Signed-off-by: Johannes Schindelin <[email protected]>
/submit |
Submitted as [email protected] |
This branch is now known as |
This patch series was integrated into pu via git@d97214f. |
This patch series was integrated into pu via git@f10e121. |
This patch series was integrated into pu via git@316f2f7. |
This patch series was integrated into next via git@d153fc0. |
This patch series was integrated into pu via git@f6f0679. |
This patch series was integrated into pu via git@2656ece. |
This patch series was integrated into next via git@2656ece. |
This patch series was integrated into master via git@2656ece. |
Closed via 2656ece. |
Turns out that I forgot a couple of spots when I sent the patch series to deprecate
git rebase -p
earlier...