On Tue, 29 Apr 2014 19:50:39 +0200, Richard Hipp <d...@sqlite.org> wrote:
File renames are uncommon in Fossil itself. See
http://www.fossil-scm.org/fossil/test-rename-list for a complete list of
all file renames that have occurred over the entire 6.78-year history of
Fossil. Renames in SQLite are similarly scarce (
http://www.sqlite.org/src/test-rename-list). Hence, diffs across renames
just a short feedback: I think keeping the `test-rename-list' would be a
welcome additional feature (even if rename-aware diff would become a
reality). at least it helps to keep track of what renames have happened at
some time or other (and thus allows to do the diff across the rename
manually if everything else fails).
have never been a priority.
for fossil "in the wild" the rating of this might be different, partly.
overall I agree that most of the time this is not an issue. but _when_ it
is it can be a serious one. I presume reorganizing a modest-size project
by moving stuff from one subdir to another could really cause
quite a bit of trouble when wanting to diff against old revisions
afterwards.
The most recent rename (on 2013-12-17) is seen here:
http://www.fossil-scm.org/fossil/timeline?n=5&c=2013-12-17+22:10:50&v
http://www.fossil-scm.org/fossil/info/8fab3e3f6ccafdb
Notice that on the diff shown on the "info" page of the check-in, it
correctly shows the changes that occurred to the file in parallel with
the
file rename.
However, if you do a diff, it shows the old file being deleted and the
new
file being added:
http://www.fossil-scm.org/fossil/vdiff?from=555c44eb5d9506e7&to=8fab3e3f6ccafdb3&sbs=1
The latter URL above can be used as a test-case when implementing
rename-aware diff.
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
