2011/9/1 Jacek Cała <jacek.c...@gmail.com> > 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. A mv+edit combination could have a non-0/100% diff, i guess. Regarding the comparison with git: git tracks changes differently, and can even tell you that a given commit moved X lines of code from file A to file B (it's pretty f-ing smart that way). Fossil tracks whole files only. i unfortunately don't understand the internal details of how fossil tracks lineage and changes well enough to explain/justify fossil's behaviour, but this topic as come up before and IIRC (which i won't guaranty!) the consensus was that fossil's design "doesn't immediately lend well" to solving that. Or maybe it's just that nobody's pitched in yet to do it. -- ----- stephan beal http://wanderinghorse.net/home/stephan/
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
