Le 22 juil. 2013 12:23, "Stephan Beal" <sgb...@googlemail.com> a écrit : > > On Mon, Jul 22, 2013 at 6:18 PM, j. van den hoff < veedeeh...@googlemail.com> wrote: >> >> Options: >> -n|--limit N Output the first N changes (default 20) >> >> where the "first" probably should be a "last" or "most recent" I'd say. > > > -n is a bit misleading, actually - that limits the number of _lines_ of output, not the number of results (i had forgotten that until now). If the limit would truncate a given commit then it finishes outputting that before ending: > > stephan@tiny:~/cvs/fossil/cwal/th1ish$ f time -n 2 > === 2013-07-21 === > 18:26:43 [77d1757a8b] *CURRENT* Added Object.toJSONString(). Still missing > overridable toJSON() support. Moved th1ish_value_XXX_part() to > cwal_value_XXX_part(). Added String.applyFormat(). (user: stephan > tags: trunk) > > stephan@tiny:~/cvs/fossil/cwal/th1ish$ f time -n 4 > === 2013-07-21 === > 18:26:43 [77d1757a8b] *CURRENT* Added Object.toJSONString(). Still missing > overridable toJSON() support. Moved th1ish_value_XXX_part() to > cwal_value_XXX_part(). Added String.applyFormat(). (user: stephan > tags: trunk) > > (same thing, but if i use -n 5 i get the next entry as well)
Actually, I've always wonder why the -n option is like this on CLI, and why it is different from the n= parameter on the webpage counterpart?. May be not a lot of people use it on the CLI? -- Martin G.
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
