(1.1) By bohwaz on 2022-04-26 00:12:07 edited from 1.0 [link] [source]Deleted
(2) By Andy Bradford (andybradford) on 2022-04-26 14:04:48 in reply to 1.1 [link] [source]
> If you happen to run `fossil stash` and then exit the editor without a > message (because your forgot something or anything else), fossil > will... revert the files, effectively destroying the work you were > trying to save Fortunately, Fossil isn't as broken as this, though bad bugs have slipped through. What actually happens is that Fossil saves the stash without a name associated. Try running "fossil stash list" and see if you find your missing code. Andy
(3) By Andy Bradford (andybradford) on 2022-04-26 23:50:33 in reply to 2 [source]
I can see how this interaction could be a bit confusing. With or without a comment, all that the "fossil stash" command says is that it reverted files. One may be led to believe that nothing happened. Yes, it has been this way for a very long time, but someone clearly got confused by the behavior and thought Fossil had destroyed work. What about something like this: https://www.fossil-scm.org/home/info/d08d7b872d33e0c4 $ f stash save -m '' REVERT file stash 12 saved This leaves no room for doubt that something may have gone wrong. Yes, it does change the output to be more verbose than before, so I can see an argument against it. Let me know what you think. Andy
(4) By sean (jungleboogie) on 2022-04-27 02:56:08 in reply to 3 [link] [source]
I’m in favor of being more verbose, especially if it prevents the assumption files have been lost.