On Nov 18, 2016, at 1:40 PM, Warren Young <war...@etr-usa.com> wrote:
>
> On Nov 18, 2016, at 12:50 PM, arnoldemu <mem...@arnoldemu.freeserve.co.uk>
> wrote:
>>
>> So I am confused. If I can add recursive, why can't I do a revert recursive?
>
> Someone Has To Do It.
I just remembered: part of this work is already done, as part of “fossil
stash.” Example, using Fossil’s own source base:
$ echo foo >> src/main.c
$ echo foo >> www/th1.md
$ fossil stash save -m 'blah' www
REVERT www/th1.md
polypore:skull tangent$ f stat
...
EDITED src/main.c
That behavior works well when you want to save the changes in a subtree of the
checkout, so you can pick up work on it later, after you finish work on the
stuff you didn’t revert.
If you just want to throw away a subtree worth of changes, you could give a
“stash save” followed by a “stash rm” to throw away the most recent stash.
Clumsy, but it would work.
Or, you could use the code that implements that subtree walking to give the
same behavior to “fossil stash revert”.
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
