2011/9/1 Stephan Beal <[email protected]>: > 2011/9/1 Jacek Cała <[email protected]> >> >> Agree, but if there's no way to view the changes, it's still a problem >> from the user perspective. > > But how should fossil diff something which (for its purposes) isn't yet > there? Agreed, though, it "could" figure out that file2 was previously > file1, and take a different diff path, but the diff is always 0% or 100%, > depending on how one defines diff to behave in the context of a mv > operation. Neither 0% nor 100% change seems useful to me in the context of a > diff.
If fossil can't process the mv+edit combination when diffing neither it moves files on disk, what is the purpose of mv then? > A mv+edit combination could have a non-0/100% diff, i guess. IMHO, this is what user (me) would actually expect. Regards, Jacek _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
