On filesystems like ZFS, OCFS2, and BtrFS it's possible to rely on copy-on-write semantics and have more than one distinct file pointing to a single copy on disk but behaving differently than a hard-link as each file can be edited independently (only allocating extra space for the changed blocks).
This could complement the -L patch (#17) for replacing identical files on the same filesystem with hard links.
On filesystems like ZFS, OCFS2, and BtrFS it's possible to rely on copy-on-write semantics and have more than one distinct file pointing to a single copy on disk but behaving differently than a hard-link as each file can be edited independently (only allocating extra space for the changed blocks).
This could complement the -L patch (#17) for replacing identical files on the same filesystem with hard links.