| commit | aa1df8146d70bb85c63b0999868fe29aebc1173e | |
| author | Phillip Wood <phillip.wood@dunelm.org.uk> | |
| Mon, 17 Oct 2022 13:17:45 +0000 (17 13:17 +0000) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Mon, 17 Oct 2022 18:53:03 +0000 (17 11:53 -0700) | ||
| tree | 8a3f340c4ab0cdcdd8e76decc533645717beb1ca | treesnapshot (tar.gz zip) |
| parent | ce5238a690821d1de230091dd6c9c13a99ed6752 | commitdiff |
rebase --keep-base: imply --no-fork-point
Given the name of the option it is confusing if --keep-base actually
changes the base of the branch without --fork-point being explicitly
given on the command line.
The combination of --keep-base with an explicit --fork-point is still
supported even though --fork-point means we do not keep the same base
if the upstream branch has been rewound. We do this in case anyone is
relying on this behavior which is tested in t3431[1]
[1] https://lore.kernel.org/git/20200715032014.GA10818@generichostname/
Signed-off-by: Phillip Wood <phillip.wood@dunelm.org.uk>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Given the name of the option it is confusing if --keep-base actually
changes the base of the branch without --fork-point being explicitly
given on the command line.
The combination of --keep-base with an explicit --fork-point is still
supported even though --fork-point means we do not keep the same base
if the upstream branch has been rewound. We do this in case anyone is
relying on this behavior which is tested in t3431[1]
[1] https://lore.kernel.org/git/20200715032014.GA10818@generichostname/
Signed-off-by: Phillip Wood <phillip.wood@dunelm.org.uk>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| Documentation/git-rebase.txt | diffblobblamehistory | |
| builtin/rebase.c | diffblobblamehistory | |
| t/t3431-rebase-fork-point.sh | diffblobblamehistory |