"Stripping" changesets from the past of a repository

[Martin Geisler]

"Jim Hewes" <jhewes at docucap.com> writes:

> Thanks, Jochen and Martin. I don't know how the hashes are calculated.
> I imagined they might be calculated from the hash of the previous
> revision plus the contents of the current one.

Exactly -- plus things like the commit message, the username, and the
date. The goal is to let the hash depend on everything in the new
changeset plus the hash value of the parent changeset(s).

> But even if that's true, you still need for the first revision to have
> a fake hash which Mercurial must ignore and make an exception for. So
> I see that it would be kludgey.

Indeed and so there's currently no support for it.

-- 
Martin Geisler

VIFF (Virtual Ideal Functionality Framework) brings easy and efficient
SMPC (Secure Multiparty Computation) to Python. See: http://viff.dk/.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://selenic.com/pipermail/mercurial/attachments/20091118/94775b41/attachment.pgp>