On Fri, Sep 11, 2015 at 6:28 PM, Warren Young <w...@etr-usa.com> wrote: > > Let me put it a bit differently than before, since I don’t seem to be > getting my point across. When you say “fossil up” and get a whole pile of > changes, your next question is, “What exactly is the content of those > changes?” This feature answers that question, and although it *happens* to > do so using the undo mechanism, the user isn’t thinking about undoing the > changes here, so why make them give a command that exposes this detail?
I see what you mean. Also, I think you missed something. It will produce a diff for any undo-able operation, not just update. Making it produce a diff specifically for the most recent update, while a useful feature, would likely be a lot more work.
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
