[apologies if shows this up twice, but I think I messed up the first time] On Mon, Nov 16, 2015 at 2:20 PM, bch <brad.har...@gmail.com> wrote: > In this sense, the behavour of git (iiuc) would be roughly what I want > where it tracks bytes, not files (this is what I think I undertand; it > allows git to track a function being moved from one file to another -- > I don't understand how it works, but it sounds like what I want -- > keep track of collections of bytes regardless of the name of their > container (the filename).
Mercurial's addremove has a --similarity option, which could be nice addition to fossil's addremove. https://selenic.com/hg/help/addremove Use the -s/--similarity option to detect renamed files. This option takes a percentage between 0 (disabled) and 100 (files must be identical) as its parameter. With a parameter greater than 0, this compares every removed file with every added file and records those similar enough as renames. Detecting renamed files this way can be expensive. After using this option, "hg status -C" can be used to check which files were identified as moved or renamed. If not specified, -s/--similarity defaults to 100 and only renames of identical files are detected. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
