Skip to content
Snippets Groups Projects
  • mpm's avatar
    ccbcc4d76f81
    fix bad assumption about uniqueness of file versions · ccbcc4d76f81
    mpm authored
    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA1
    
    fix bad assumption about uniqueness of file versions
    
    Mercurial had assumed that a given file hash could show up in only one
    changeset, and thus that the mapping from file revision to changeset
    was 1-to-1. But if two people perform the same edit with the same
    parents, we can get an identical hash in different changesets.
    
    So we've got to loosen up our uniqueness checks in addgroup and in
    verify.
    
    manifest hash: 5462003241e7d071ffa1741b87a59f646c9988ed
    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.0 (GNU/Linux)
    
    iD8DBQFCoMDkywK+sNU5EO8RAg9PAJ9YWSknfFBoeYve/+Z5DDGGvytDkwCgoMwj
    kT01PcjNzGPr1/Oe5WRvulE=
    =HC4t
    -----END PGP SIGNATURE-----
    ccbcc4d76f81
    History
    fix bad assumption about uniqueness of file versions
    mpm authored
    -----BEGIN PGP SIGNED MESSAGE-----
    Hash: SHA1
    
    fix bad assumption about uniqueness of file versions
    
    Mercurial had assumed that a given file hash could show up in only one
    changeset, and thus that the mapping from file revision to changeset
    was 1-to-1. But if two people perform the same edit with the same
    parents, we can get an identical hash in different changesets.
    
    So we've got to loosen up our uniqueness checks in addgroup and in
    verify.
    
    manifest hash: 5462003241e7d071ffa1741b87a59f646c9988ed
    -----BEGIN PGP SIGNATURE-----
    Version: GnuPG v1.4.0 (GNU/Linux)
    
    iD8DBQFCoMDkywK+sNU5EO8RAg9PAJ9YWSknfFBoeYve/+Z5DDGGvytDkwCgoMwj
    kT01PcjNzGPr1/Oe5WRvulE=
    =HC4t
    -----END PGP SIGNATURE-----