On Mon, 2 May 2005, Davide Libenzi wrote: > On Mon, 2 May 2005, Linus Torvalds wrote: > >> Yes. EXCEPT for one thing. fsck. I'd _really_ like fsck to be able to know >> something about any xdelta objects, if only because if/when things go > Linus, xdelta-based algorithms already stores informations regarding the > object that originated the diff. Since they have no context (like > text-based diffs) and are simply based on offset-driven copy/insert > operations, this is a requirement. Libxdiff uses an adler32+size of the > original object, but you can get as fancy as you like in your own > implementation. Before a delta patching, the stored information are cross > checked with the input base object, and the delta patch will fail in the > eventuality of mismatch. So an fsck is simply a walk backward (or forward, > depending on your metadata model) of the whole delta chain. Linus knows this. His point is just to be sure you actually *code* that walk in fsck, and (hopefully) do so w/o complicating the fsck too much. --scott supercomputer BOND quiche SYNCARP Honduras North Korea Qaddafi PANCHO SKILLET KUDESK non-violent protest ESQUIRE struggle Saddam Hussein ( http://cscott.net/ ) - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.htmlReceived on Wed May 04 01:54:00 2005
This archive was generated by hypermail 2.1.8 : 2005-05-04 01:54:30 EST