On 5/10/2017 8:54 PM, Ron Aaron 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".
The help also says "-r REVISION revert given FILE(s) back to given
REVISION", which strongly implies that it can only be used with a single
file at a time.
But in my experience, fossil revert is a rarely used command.
Each file it reverts is edited in the current workspace to have the
content it did at that version. Those edits are usually changes that
would subsequently need to be committed. The only time they are not, is
when the revision xxx is the same version as the workspace itself; thus
editing the file to put it back before you accidentally broke it with
some other command.
This often does make sense when you merge from the wrong branch by
mistake or need to repair damage caused to a file by local uncommitted
changes.
But I've rarely used it.
Is it possible you really wanted "fossil update xxx" instead?
That would make all the changed needed on disk to move the current
working copy to revision xxx. It isn't an edit. You simply have a check
out at that revision level. This is a command that is frequently used to
hop between trunk and branches, or to go back to a version that has a
bug report to reproduce it locally in exactly the version the reporter has.
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 626 303 1602
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
