On 20/04/2013, at 2:46 AM, Richard Hipp <d...@sqlite.org> wrote: > > > On Fri, Apr 19, 2013 at 1:19 PM, Stefan Bellon <sbel...@sbellon.de> wrote: > On Fri, 19 Apr, Jan Nijtmans wrote: > > > Yes, that would work fine. My question was not meant technical, but > > regarding the documentation: If "--test|-n" is the new 'official' > > option, and "--nochange" is deprecated, the documentation should be > > adapted accordingly as well. > > If changing (and possibly breaking existing scripts), why not change it > to something *really* meaningful and use something other tools use, > e.g. make: > > -n, --just-print, --dry-run, --recon > Don't actually run any commands; just > print them. > > -n as short and --dry-run as long option seem like a good choice. > > I can go with --dryrun (I think without the "-" between "dry" and "run", but > that is a minor point that I won't insist on.)
I'm all for re-inventing square wheels, but given svn, rsync, git (and perhaps others) use -n and --dry-run it would be worth using those Steve _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
