Duy Nguyen <pclouds@xxxxxxxxx> writes: > I've changed my mind. I'm not using --index and --cached for "git > restore" (formerly "git restore-files"). So how about this? > > git restore --from=<tree> <pathspec> will update both the index and worktree. > > git restore --from=<tree> --keep-index <pathspec> will not update the index > > git restore --from=<tree> --keep-worktree <pathspec> will not update worktree An action to "restore" with an option to "keep" (i.e. "do not touch") smells strongly of double negation. We are restoring, i.e. grabbing something that existed in the past out of another place (like tree or index) and depositing it to the working tree to recover its previous state, oh, not but not touching the content of the working tree (or the index) intact? It would be great if you can come up with phrasing that avoids specifying what is *not* done, but instructs the command what is to be done, perhaps along the lines of "restore --index-only", "restore --worktree-only" and "restore --index-and-worktree (which would be the default)".
