sapling/hgext/pushrebase
Durham Goode 39d85694ed pushrebase: don't prepopulate manifest caches
Summary:
This had a nasty bug where it manually computed the cached base text
using the full manifest text. When operating in a treeonly repository, this
resulted in corrupt deltas. The only reason we didn't hit it earlier is because
the secondary stackpush path was added and doesn't have this issue. But it
couldn't handle merge commits, which is why we hit this when it came time to add
a merge commit.

Now that the main repo that needed this optimization is treeonly, we don't need
this precaching anymore.

Reviewed By: mitrandir77

Differential Revision: D13154342

fbshipit-source-id: 5cb74167665a60a36e4a6d926f3f9f1c5c7bbef1
2018-11-21 08:33:48 -08:00
..
__init__.py pushrebase: don't prepopulate manifest caches 2018-11-21 08:33:48 -08:00
errors.py pushrebase: introduce a stackpush fast path 2018-09-25 16:06:21 -07:00
recording.py pushrebase: record pushrebases failed on hooks 2018-10-03 04:20:22 -07:00
stackpush.py pushrebase: introduce a stackpush fast path 2018-09-25 16:06:21 -07:00