On 9/23/17, Andy Goth <[email protected]> wrote: > > I tried this, only to find that annotate only works when given a > manifest in which a file actually changed. Otherwise I get this error: > > file #631 is unchanged in manifest #37365 >
Proposed changes: (1) Move the fix for the error above inside of the annotate_file() routine. In other words, have annotate_file() automatically seek out the checkin containing the most recent change to the file. (2) Move the call to compute_direct_ancestors() inside of annotate_file(). (3) Add a new parameter to annotate_file() which is the "destination" of the search. If "destination" is 0, then it does an ordinary annotation for all direct ancestors of "mid". But if "destination" is non-zero then it does an annotation of changes along the shortest patch from "mid" to "destination". (4) Given the changes above, it should be relatively simple to add switches to the "annotate" command, and new query parameters to the /annotate webpage, to do a reverse annotation. -- D. Richard Hipp [email protected] _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
