-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 09/01/2011 06:17 PM, Stephan Beal wrote:
> 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. AIUI, both git and fossil store each commit as a full tree; such cleverness is purely in the hands of the diff algorithm... - -- Alaric Snell-Pym http://www.snell-pym.org.uk/alaric/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk5gsC0ACgkQRgz/WHNxCGqF2wCfaB8KJO4x6qH5i2RD5IgVt0Iw zXUAnRdpYBLMjRZpyJ0L7YKHFIsrOczM =gLts -----END PGP SIGNATURE----- _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
