The "annotate" and "blame" features are very useful for figuring out when some piece of code was added to the current head. But sometimes I want to figure out when some piece of code was deleted from an historical version of code.
A concrete example: Earlier today I needed to know which check-in deleted the lines of code shown at http://www.sqlite.org/src/artifact/21a36fa0b375?ln=4184-4188 from SQLite. I found my answer by doing a binary search of all historical versions of that file from the version shown above to present. And that worked, but it was tedious. So, I'd like to add an "inverse annotate" feature which works like "annotate" but instead of looking backwards in time and tagging each line of code with the check-in where it was most recently modified, the output looks forward in time and shows the first subsequent check-in where that line was modified or deleted. The implementation of this is probably straight-forward. Just run the annotate algorithm forwards in time rather than backwards. My question: What do I call it? QUESTION: What do I call the hyperlink that shows "annotate/blame" only forwards in time instead of backwards in time. -- D. Richard Hipp d...@sqlite.org
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
