Sorry, but I can't see how the terminology "... all files if no file name is provided" could mean anything but what I assumed.
It may not be used often, but in the event were one has decided, as I
did, that a certain number of trunk changes (as in: the last 7) need to
be reverted, it is what one would expect to be able to use. That is,
"revert not just one file, but all files, to a given revision".
Yes, I can "upd XXX" to get back to XXX. But since I want the continued
development to be from there on, but I don't want to branch, I have two
options if 'revert' doesn't work:
1. Do "merge --backout" in reverse order for each of the N revisions I
want to remove, or
2. Do "upd XXX" and then "ci --allow-fork", than "upd trunk" and "merge
that-branch" and then close that-branch
Neither is nearly as simple and intuitive as "revert".
No, I didn't want to update to that revision, I wanted to replace the
tip with that revision.
On 05/11/17 07:35, Ross Berteig wrote:
> 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.
>
*Ron Aaron | * CTO Aaron High-Tech, Ltd <http://8th-dev.com> | +1
425.296.0766 / +972 52.652.5543 | GnuPG Key: 91F92EB8
<https://pgp.mit.edu/pks/lookup?op=get&search=0xC90C1BD191F92EB8>
<<attachment: ron.vcf>>
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
