Fossil SCM
shash pop will drop the stash even if it could not apply it.
fbfe43e153ee0e1…
· opened 15 years, 2 months ago
- Type
- Code_Defect
- Priority
- —
- Severity
- Severe
- Resolution
- Fixed
- Subsystem
- —
- Created
- Jan. 24, 2011 4:40 p.m.
Hello,
Say that my FOSSIL file is in /home/project1
I am in /home/project1/foo
fossil changes tells me that foo/bar/baz.txt and bar/foo/baz.txt have both changed. What it lists are paths relative to the directory where FOSSIL is. Those paths are not relative to my CWD.
fossil stash save -m hello foo/bar/baz.txt should fail because it expects a path relative to the CWD, but it will revert both files and make a stash from them.
Then, fossil stash pop, which seems to expect me to be at the root of the working tree, will try to apply the stash, fail to do it, but still drop it, potentially losing work. It should have kept the stash because it could not apply it.
I was lucky to have a recent diff generated by fossil with which I was able to recover my work (two days).