On 2017-04-12 01:46, Ross Berteig wrote:
In any case, you don't generally want to do addremove and commit in a single operation because that doesn't give you a chance to review (and test) what it decided to add and remove before it is committed to immutable history.
That's certainly true for a public open source project but I wouldn't do it for an internal one.
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
