On Fri, Apr 19, 2013 at 7:32 AM, Jan Nijtmans <[email protected]>wrote:
> 2013/4/19 Richard Hipp <[email protected]> > >> I prefer --test over --nochange. That seems more to the point of what >> the option is intended for. >> >> > So, is it OK to change > > fossil merge --nochange ... > fossil update --nochange ... > to > fossil merge --test ... > fossil update --test ... > then? > > How should we deal with: > - Keeping "--nochange" as deprecated alternative for now? > - Keeping "-n" as short alternative? > Would this not work? nochangeFlag = find_option("test","n",0)!=0 || find_option("nochange",0,0)!=0; -- D. Richard Hipp [email protected]
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
