* Richard Hipp <d...@sqlite.org> [20121120 01:13]: > On Mon, Nov 19, 2012 at 6:12 PM, j. v. d. hoff > <veedeeh...@googlemail.com>wrote: > > > -- fossil timeline: I find this really hard to read and use for at least > > two reasons: > > > > I seldom use "fossil timeline", preferring instead to run "fossil ui" and > look at the timeline with the graph in my web-browser. Am I the only one > that thinks this way?
Well, I use fossil in many places where I can't easily use "fossil ui" (no graphic environment). Even when if available, I tend to use it only because I've yet ito find out how to quickly go from "fossil timeline" to "let me see how file F changed in changeset C" in the command line. I'd suggest an option to include more vertical space, even if it breaks the current one-line-per-commit paradigm. Also, an option as in "hg log --patch -r 123" (show me the patch corresponding to that version) > > > > > -- the `fossil diff --from rev1 --to rev2' syntax deviates from the much > > more common (and easier to type `-r rev1:rev2') for no good reason I can > > see. > > > > You think that "-r rev1:rev2" is more intuitive than "--from rev1 --to > rev2"? Really? If it's important, we could add it as alternative syntax, > I suppose. But what would you do if the name of rev1 contained an embedded > colon? Do we have to invent some kind of escape syntax to accompany this > notation? No more intuitive, but shorter and "more standard". Instead of an escape syntax, I understand that forbidding ':' from branch names would suffice? thanks -- pica _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
