checkout/restore: refuse unmerging paths unless checking out of the index
Recreating unmerged index entries using resolve-undo data, recreating conflicted working tree files using unmerged index entries, and writing data out of unmerged index entries, make sense only when we are checking paths out of the index and not when we are checking paths out of a tree-ish. Add an extra check to make sure "--merge" and "--ours/--theirs" options are rejected when checking out from a tree-ish, update the document (especially the SYNOPSIS section) to highlight that they are incompatible, and add a few tests to make sure the combination fails. Signed-off-by: Junio C Hamano <gitster@pobox.com>
This commit is contained in:
@ -520,6 +520,15 @@ static int checkout_paths(const struct checkout_opts *opts,
|
||||
"--merge", "--conflict", "--staged");
|
||||
}
|
||||
|
||||
/*
|
||||
* recreating unmerged index entries and writing out data from
|
||||
* unmerged index entries would make no sense when checking out
|
||||
* of a tree-ish.
|
||||
*/
|
||||
if ((opts->merge || opts->writeout_stage) && opts->source_tree)
|
||||
die(_("'%s', '%s', or '%s' cannot be used when checking out of a tree"),
|
||||
"--merge", "--ours", "--theirs");
|
||||
|
||||
if (opts->patch_mode) {
|
||||
enum add_p_mode patch_mode;
|
||||
const char *rev = new_branch_info->name;
|
||||
|
Reference in New Issue
Block a user