> (b) while I depend on the fact that if the SHA of an object matches, the
> objects are the same, I generally try to avoid the reverse
> dependency.
It might be a valid point that you want to leave the door open to using
a different (than SHA1) digest. (So this means you going to store it
as an ASCII string, right?)
But I don't see how that applies here. Any optimization that avoids
rereading old versions if the digests match will never trigger on the
day you change digests. No problem here - you doomed to reread the old
version in any case.
Either you got your logic backwards, or I need another cup of coffee.
--
I won't rest till it's the best ...
Programmer, Linux Scalability
Paul Jackson <[email protected]> 1.650.933.1373, 1.925.600.0401
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
