On 5/10/17, Ron Aaron <r...@aaron-tech.com> wrote: > I tried to revert to a good revision 'xxx' using "fossil revert -r xxx" > > Despite the help stating "Revert all files if no file name is provided", > instead fossil told me, "the --revision option does not work for the > entire tree".
Amid all the confusion, I'm not sure this question was ever answered. So let me now try... The "fossil revert" command is intended to undo edits to the local check-out and restore the content of files back to the last committed version. For example, you start making some change and decide that your idea isn't really working out, so you type "fossil revert" to take you back to a pristine state. Or you do "fossil revert $filename" to undo all of the local edits for a particular file while retaining the edits to other files. The "fossil revert" command only affects the local check-out. It makes no changes to the repository. If you want to move your whole check-out to a different baseline, better to do so using: fossil revert fossil update $newbaseline If you want to change a single file to be the same as it was several check-ins ago, better to do something like this: fossil artifact $hash >$filename In other words, look up the cryptographic hash for the version of the file you want, then just overwrite the local copy with this historical copy. -- D. Richard Hipp d...@sqlite.org _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users