revlog.addrevision(): move computation of nodeid in addrevision() The check "if node in nodemap" is already done earlier in addgroup().

contrib/compress: compress should activate parentdelta

contrib/compress: correct ordering of copying Changelog should always be copied last, otherwise readers can see an inconsistent repo.

contrib/compress: refactor revlog copying

contrib/compress: use store API instead of a collector

contrib/compress: proper lock handling Lock the src repo before beginning the compression and lock the destination repo before copying the revlogs. Proper handling of exceptions.

contrib/compress: use hg API to compute the destination path

contrib/compress: use repo's transaction method

contrib/compress: remove unused variables

tests: unify test-hgrc

tests: remove test-log.out, useless after unification

revlog: fix docstring

deltaparent(): don't return nullrev for a revision containing a full snapshot this allows us to simplify manifest.readdelta and revlog.revdiff

merge with stable

tests: fix up bisect test output

merge: move reverse-merge logic out of filemerge (issue2342)

bisect: add test for unrelated starting revisions

merge with stable

bisect: better message for unrelated starting revisions

debuginstall: report installpath

tests: unify test-glog

bookmarks: fix long line

merge with stable

revlog: addgroup re-adds punched revisions for missing parents While reading changegroup if a node with missing parents is encountered, we add a punched entry in the index with null parents for the missing parent node.

revlog: generate full revisions when parent node is missing The full revision is sent if the first parent, against which diff is calculated, is missing at remote. This happens in the case of shallow clones.

revlog.revision(): inline deltachain computation

revlog.revision(): remove debug code

revlog.revision(): don't use nullrev as the default value for the cache I is probably a bug if the deltachain computation think there was a cache hit at nullrev. Use None instead, this will never trigger a cache hit.