>I did cp -rl his-tree my-tree (which completed >quickly), edited the two files that needed to be patched, then did >diff -urp his-tree my-tree, which also completed quickly, as diff knows >that if two files have the same inode, they don't need to be opened. >... download one tree from kernel.org, do a bunch of cp -lr for >each arch you plan to play with, and then go and work on each of the trees >separately. Cool. It's like a poor man's directory overlay (same basic concept as union mount, Make's VPATH, and Subversion branching). And I guess this explains why the diff optimization is so important. -- Bryan Henderson San Jose California IBM Almaden Research Center Filesystems - To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
