On Wed, Jan 30, 2013 at 02:48:33PM -0800, Arnel Legaspi wrote: > Hello - > > Yesterday I needed to revert back a commit involving 2 files to its parent > commit. > The working copy was at the tip (1255785c96) and I needed to get back to > revision 4002407825. > When I tried running "fossil revert -r 4002407825" I got the following > error: > > fossil: the --revision option does not work for the entire tree > > What did the trick was "fossil merge --backout 1255785c96" which is > strange, since this is not a merge. > The timeline UI for this particular repo shows a straight line graph. > > Shouldn't the 'revert' command act the way I was looking for? The help > message does state > "Revert all files if no file name is provided." What am I missing?
Reverts removes changes in your *working directory*. It's not about "reverting code already checked int". You want 'fossil merge -backout' I guess. The help for merge explains better. Regards, Lluís. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
