Suppose it's Monday morning (like...5 minutes ago) and you committed all your changes on Friday afternoon. You come in on Monday and use the handy `fossil diff --tk` feature to see if you left anything uncommitted last week.
When there are no outstanding changes and you `fossil diff --tk`, it just hangs. I think the software should behave as it does for `fossil diff`, which just quits. Note that one could also argue for a message like "No differences between checkout and repository" to be printed to the console, perhaps on stderr, in order to give more situational awareness. Thanks! _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
