Hi, On Wed, 4 Apr 2007, Rogan Dawes wrote: > Andy Parkins wrote: > > > As an example: compress a file, change a byte, compress it again, > > perform a binary diff; what is that diff telling you about the change? > > (My answer is: not much). > > Well, at least as much as the resulting sizes tell you, if not more. The subtle difference: your approach is _expensive_ in terms of CPU time, while the byte change approach is _dirt cheap_. Since it seems that there are gazillions of examples where one or the other (or both) do not make sense, I'd rather have the fast one. HOWEVER, there is something I really would like to have, namely a clear distinction between new file / deleted file, and 0->n / n->0 changes. Ciao, Dscho - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html