summaryrefslogtreecommitdiff
path: root/Documentation/glossary-content.txt
diff options
context:
space:
mode:
authorLibravatar Elijah Newren <newren@gmail.com>2018-07-27 12:59:44 +0000
committerLibravatar Junio C Hamano <gitster@pobox.com>2018-07-27 11:15:20 -0700
commit2b75fb601c05a789988cf0e1b3c1375ee62d3c3e (patch)
tree5aec8bab804e1259b7d0acb80f9c505d107e0235 /Documentation/glossary-content.txt
parentt3507: add a testcase showing failure with sparse checkout (diff)
downloadtgif-2b75fb601c05a789988cf0e1b3c1375ee62d3c3e.tar.xz
merge-recursive: preserve skip_worktree bit when necessary
merge-recursive takes any files marked as unmerged by unpack_trees, tries to figure out whether they can be resolved (e.g. using renames or a file-level merge), and then if they can be it will delete the old cache entries and writes new ones. This means that any ce_flags for those cache entries are essentially cleared when merging. Unfortunately, if a file was marked as skip_worktree and it needs a file-level merge but the merge results in the same version of the file that was found in HEAD, we skip updating the worktree (because the file was unchanged) but clear the skip_worktree bit (because of the delete-cache-entry-and-write-new-one). This makes git treat the file as having a local change in the working copy, namely a delete, when it should appear as unchanged despite not being present. Avoid this problem by copying the skip_worktree flag in this case. Signed-off-by: Elijah Newren <newren@gmail.com> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 'Documentation/glossary-content.txt')
0 files changed, 0 insertions, 0 deletions