On 22 January 2014 12:23, Richard Hipp <d...@sqlite.org> wrote: > >> michai@lime:~/src/068-lighting_fundamentals_sls$ f timeline -n 4 >> === 2014-01-22 === >> 07:34:13 [0a6b833945] *CURRENT* added Y (user: michai tags: trunk) >> 07:33:27 [fb73686d55] changed X (user: michai tags: trunk) >> 07:32:56 [84ef6a7729] added X (user: michai tags: trunk) >> === 2014-01-21 === >> 22:40:48 [959ae30958] bla >> --- entry limit (4) reached --- >> >> then vdiff-command >> >> http://myhost/myrepo/vdiff?from=2014-01-22T07:30&to=tip&sbs=1 >> >> ... yields: >> >> Added X version [1f772307fb6a8db8] >> <the diff belonging to [fb73686d55] instead of [84ef6a7729]> > > > I don't understand what you mean by a diff "belonging to" a version? A diff > is between two versions, not one. Which two versions of the file X are > being diffed in this case? > >> >> Added Y version [547cf73a9fb9bdb9] >> <the diff correctly belonging to [0a6b833945]>
[0a6b833945] is the checkin adding file Y (only that). In the suspect case, the diff belonging to checkin [fb73686d55] (change of file X, nothing else) was displayed under the checkin-description of checkin [84ef6a7729] (the checkin adding file X, and nothing else). What I meant to say: mostly I'm interested in modifications rather than added/deleted files; when visually going over the list produced by vdiff&sbs=0, some modifications are not listed (if another checkin is present in the list which was used to add the initial file). Michai _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
