On 12/10, Duy Nguyen wrote: > On Sun, Dec 9, 2018 at 9:05 PM Thomas Gummerer <t.gummerer@xxxxxxxxx> wrote: > > > > Currently when 'git checkout -- <pathspec>...' is invoked with > > multiple pathspecs, where one or more of the pathspecs don't match > > anything, checkout errors out. > > > > This can be inconvenient in some cases, such as when using git > > checkout from a script. > > Wait, should scripts go with read-tree, checkout-index or other > plumbing commands instead? Possibly. As mentioned in an other email, we do seem to have some scripts in git.git that are using 'git checkout' already, but they are using it in the checkout branch mode, rather than the checkout paths mode that I would like to use it in git-stash. But with the rewrite of 'git stash' in C, maybe this step is moot anyway, and we can just call the checkout_paths function internally without using the run_command API at all. We could then have an internal mode for ignoring unmatched pathspecs that we wouldn't need to expose to users. > -- > Duy
