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>
This commit is contained in:

committed by
Junio C Hamano

parent
ce5238a690
commit
aa1df8146d
@ -1230,6 +1230,12 @@ int cmd_rebase(int argc, const char **argv, const char *prefix)
|
||||
die(_("options '%s' and '%s' cannot be used together"), "--keep-base", "--onto");
|
||||
if (options.root)
|
||||
die(_("options '%s' and '%s' cannot be used together"), "--keep-base", "--root");
|
||||
/*
|
||||
* --keep-base defaults to --no-fork-point to keep the
|
||||
* base the same.
|
||||
*/
|
||||
if (options.fork_point < 0)
|
||||
options.fork_point = 0;
|
||||
}
|
||||
/*
|
||||
* --keep-base defaults to --reapply-cherry-picks to avoid losing
|
||||
|
Reference in New Issue
Block a user