Thus said "Andy Bradford" on 05 Oct 2014 23:18:01 -0600: > On the other hand, the case of fossil update -s seems clear enough, > just run the update and exit non-zero if no updates were made.
By the way, I'm not not necessarily suggesting that this be done. At the moment, fossil update does exit non-zero if there are sync errors (e.g. password failure, database locked, other remote server errors, etc...). I simply meant that -s as a use case makes more sense than a --dry-run that does faux sync operations. Andy -- TAI64 timestamp: 4000000054322a12 _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
