On Sat, 18 Oct, Richard Hipp wrote: > Are we ready to merge this enhancement into trunk? Are there any > objections to the new command-line timeline capability?
I see a regression regarding previous behaviour. Our scripts use the following two-step process in order to see the timeline of a branch, clipped to only that branch starting from the most recent checkin to the branch: $ fossil timeline $BRANCH -n 1 -t ci Then "grep" out the commit id from that output and follow with $ fossil timeline ancestors $COMMIT_ID -n 2147483647 -t ci in order to get the full timeline. Now with the recent trunk build, I get: $ fossil timeline trunk +++ no more data (0) +++ $ This seems a regression to me. BTW: If there's an easier way to get at that information in one call, feel free to point it out to me as well. ;-) Greetings, Stefan -- Stefan Bellon _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
