> One of the thinks that I most dislike of other VCS is the excess of > options. Too many options means to much time reading the manuals and > to much time remembering the possibilities of the tool. > > Fossil is very good at it. It has the minimum set of options to make the > tool useful. > > In my opinion, "fossil -M file commit" falls clearly into this > category. I do not see it useful for scripting or external tools, as > these tools can perfectly use the "-m message" option. And for the > casual user, DRH option of saving automatically the comment and > inserting it in the new > commit is much more clever. > > An option that I would like to see in fossil, as it is not easy to > perform in fossil without changing any file is a way to know what an > update would do without actually doing it. > > I see two ways of doing it: > > fossil --dry-run update > > or > > fossil changes ?version? > > In the last case, there should be an easy way of knowing which is the > version to which fossil would update by default > > RR
Sometimes I wish for such a feature also. I think the following syntax similar to pkzip would be clear: fossil commit --test fossil update --test etc. RW Ron Wilson, Engineering Project Lead (o) 434.455.6453, (m) 434.851.1612, www.harris.com HARRIS CORPORATION | RF Communications Division assuredcommunications(tm) _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
