Hi Junio, On Mon, 28 Oct 2019, Junio C Hamano wrote: > Johannes Schindelin <Johannes.Schindelin@xxxxxx> writes: > > > On Thu, 26 Sep 2019, Johannes Schindelin via GitGitGadget wrote: > > > >> My colleague Dan Thompson reported a bug in a sparse checkout, > >> where git stash (after resolving merge conflicts and then making up > >> their mind to stash the changes instead of committing them) would > >> "lose" files (and files that were not even in the sparse checkout's > >> cone!). > > > > I only realized _now_ that this patch has not made it anywhere. > > Yeah, I do not recall seeing any of the patches in the topic (nor > the cover letter). It is not clear to me what "lose" above means, > which is an indication that I didn't read the topic a month ago X-<. Sorry, in this context, "to lose a file" means that a `git stash` would record such a file as deleted. A subsequent `git stash apply` _would_ then delete it. > Did it even get any review by skip worktree bit experts back then? Sadly, it did not get any review back then... Ciao, Dscho
