Hello,

When not at the root of a working set, but in a subdirectory, fossil stash pop will apply nothing because it cannot figure out what files are to be patched, but it will still delete the stash.

This nearly led me to lose two days of work, but fortunately I had a very recent <tt>fossil diff</tt> result nearby with which I could patch.

Additionnally, when doing <tt>fossil stash save -m "some comment" a/list/of/paths/relative/to/the/working/set/root and not at the root, fossil will not verify that the list of files is valid and will revert every single changed file.

So, say that my <tt>_FOSSIL_</tt> file is in /home/project1

I am in /home/project1/foo

<tt>fossil changes</tt> tells me that foo/bar/baz.txt and bar/foo/baz.txt have both changed.

<tt>fossil stash save -m hello foo/bar/baz.txt</tt> will revert both files because it expects a relative path, but it should fail.

Then, <tt>fossil stash pop</tt> will apply nothing because it cannot locate the files in the stash relative to the CWD, and lose any change.

shash pop will drop the stash even if it could not apply it.