Updating the currently checked out branch may cause confusion
When checking out paths from the index, this option lets you recreate the conflicted merge in the specified paths.
--conflict= The same as --merge option above, but changes the way the conflicting hunks are presented, overriding the merge.conflictstyle configuration variable.
Local modifications to the files in the working tree are kept, so that they can be committed to the .
If you want to start a disconnected history that records a set of paths that is totally different from the one of , then you should clear the index and the working tree right after creating the orphan branch by running "git rm -rf ." from the top level of the working tree.
Afterwards you will be ready to prepare your new files, repopulating the working tree, by copying them from elsewhere, extracting a tarball, etc.
--ignore-skip-worktree-bits In sparse checkout mode, git checkout -- .
-m, --merge When switching branches, if you have local modifications to one or more files that are different between the current branch and the branch to which you are switching, the command refuses to switch branches in order to preserve your modifications in context.