Thus said Ross Berteig on Wed, 10 Feb 2016 15:48:40 -0800:
> which as expected renamed the file in the repository but not on the
> disk. It then says
>
> fossil stash -m "B 2016-02-09"
Did you mean:
fossil stash save -m "B 2016-02-09"
> ERROR: no such file: c:/Users/Ross/Documents/tmp/fbuild/stash/f1new
>
> What was fossil stash supposed to do in this circumstance?
It marked the file as being renamed but did not change the disk, as
documented in ``fossil help mv'':
WARNING: If the "--hard" option is specified -OR- the "mv-rm-files"
setting is non-zero, files WILL BE renamed or moved on disk
as well. This does NOT apply to the 'rename' command.
Options:
--soft Skip moving files within the checkout.
This supersedes the --hard option.
--hard Move files within the checkout.
You asked Fossil to prepare the repository for a file move, but never
moved the files. Then when you attempted to stash the change, Fossil
complained because it expected to find f1new, but you never renamed f1
to f1new. If you had also then done ``fossil status'' it would have
reported f1new as MISSING.
Andy
--
TAI64 timestamp: 4000000056bc2d39
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
