On 09/23/17 12:29, Andy Goth wrote:
The [annotate] command line and web interfaces take totally different
approaches to identifying which version to work with. The web
interface simply asks the user, whereas the command line interface
seems to take the long way around. If I'm reading this code
correctly, it finds both the current check-in and the check-in that
most recently modified the file, then uses these two values
separately.
Why not make the command line interface code more closely match the
web interface code? Let the annotate command accept a -r option to
override the current check in for the value of mid, then proceed the
same as the web interface code.
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
So I had more work ahead of me. It's all done now though:
http://fossil-scm.org/index.html/info/5a6b194bc900eb00
Please give this a try and let us know how it works for you.
I don't think it's worth adding a -R option to annotate since there
isn't one for diff.
--
Andy Goth | <andrew.m.goth/at/gmail/dot/com>
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
