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 revision 911804.

- Julian

> There was agreement on always using SHA1 hashes in the 'pristine store
> design' thread. See where Greg says "nono" in
> http://mail-archives.apache.org/mod_mbox/subversion-dev/201002.mbox/%3C6cca3db31002171652u15ae7e87ha5b09e4cb170af2a@mail.gmail.com%3E
>
> The possibility of using MD5 to index was also named in that thread, but did
> not resonate well.
>
> ~Neels
Received on 2010-02-19 14:14:36 CET