Hmm, I happen to use the REVERT command *all* the time. It's the simplest
(and possibly only direct) way I know to quickly abort all changes (after
experimenting with code) and go back to what was the check-in. How do the
rest of you do an abort?
I must admit I very rarely used the -r option, though. But I have certainly
needed a quicker way to backout multiple check-ins in one go (if this was
supported), rather than one at a time.
-----Original Message-----
From: Richard Hipp
Sent: Thursday, May 11, 2017 2:03 PM
To: Fossil SCM user's discussion
Subject: Re: [fossil-users] Problem with: fossil revert -r xxx
On 5/11/17, Ross Berteig <r...@cheshireeng.com> 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"
But in my experience, fossil revert is a rarely used command.
Yeah. In fact, I didn't even remember that there was a 'revert'
command. And even now, I'm not entirely clear what it does, or what
it is intended to do.
The original "revert" command was added on 2007-09-24 (very early in
Fossil's history) by user "jnc" - I'm not sure who that is.
I have just now checked in a change to moves the "revert" command off
of the "fossil help" menu, so that you now only see it when you do
"fossil help --all".
--
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
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
