Re: [PATCH] Define PRISTINE.checksum as always being SHA-1

Neels J Hofmeyr wrote: > Julian Foad wrote: > > Bert and I were just discussing the checksums in PRISTINE. We think its > > primary key should be SHA-1 always. A secondary index can be built on > > the MD5 column if required. > > > > Can we patch the docco like this? > > +1 OK, Committed revisio

Re: [PATCH] Define PRISTINE.checksum as always being SHA-1

Julian Foad wrote: > Bert and I were just discussing the checksums in PRISTINE. We think its > primary key should be SHA-1 always. A secondary index can be built on > the MD5 column if required. > > Can we patch the docco like this? +1 There was agreement on always using SHA1 hashes in the 'pris

[PATCH] Define PRISTINE.checksum as always being SHA-1

Bert and I were just discussing the checksums in PRISTINE. We think its primary key should be SHA-1 always. A secondary index can be built on the MD5 column if required. Can we patch the docco like this? [[[ * subversion/libsvn_wc/wc-metadata.sql (PRISTINE): Define "checksum" as always being SH