- Aug 21, 2018
-
-
Pierre-Yves David authored
Topic is untouched so we keep the previous version number.
-
Pierre-Yves David authored
-
Pierre-Yves David authored
-
Dan Villiom Podlaski Christiansen authored
The previous help string generally had a highly technical language. I've tried my best to address that.
-
Dan Villiom Podlaski Christiansen authored
The previous help string for prune didn't mention successors in the first line. Note: Pierre-Yves David changed the original "hidden" to "obsolete" as it is better concept to put forward. (a bit more specific and with more consequence than just "hidden"). We need a good `hg help obsolete/obsolescence` result. We'll try to get this in the next version.
-
Pierre-Yves David authored
I hope this highlight the use case for all three options.
-
Pierre-Yves David authored
The --biject flag seems a less common use case.
-
Pierre-Yves David authored
Field testing show it save people one wrong call often enough that it is worth keeping.
-
Dan Villiom Podlaski Christiansen authored
-
Dan Villiom Podlaski Christiansen authored
Extracted by Pierre-Yves David
-
- Aug 20, 2018
-
-
Pulkit Goyal authored
We didn't use to delete the evolvestate after aborting an interrupted `next --evolve`. This patch makes sure we do that. The test changes demonstrate the fix and we add a CHANGELOG entry about the fix.
-
Pulkit Goyal authored
This patch adds test to check whether we delete the evolvestate correctly after aborting or stopping an interrupted evolve which is caused because of `next --evolve`.
-
Pierre-Yves David authored
-
- Aug 18, 2018
-
-
Pulkit Goyal authored
This patch makes sure we set the second parent correctly if we run into conflicts while evolving. Also, we need to make sure to reset to one parent before committing.
-
Pulkit Goyal authored
We use node as a variable name at few places and the conflicts with variable name are not good. Moreover this practice is followed in core mercurial also.
-
Pulkit Goyal authored
This patch adds a test to demonstrate issue5927 which is about evolving not setting p2 correctly in interruption.
-
- Aug 17, 2018
-
-
Pierre-Yves David authored
For some reason the check in repo is not working for stable sort. We also force firstmerge to be saved as test show it was missing.
-
Pierre-Yves David authored
This test reveal that multiple cache are not saved to disk after discovery (firstmerge, stablesort).
-
Pierre-Yves David authored
This one does not introduce inconsistency but helps performance. G: changed hgext3rd/evolve/stablerangecache.py
-
Pierre-Yves David authored
If the on disk date cover different area, the invalidation of affected range will misbehave.
-
Pierre-Yves David authored
Clearing on disk data in nice, but we also need to remove in memory one or we'll get incorrect results.
-
- Aug 16, 2018
-
-
Pierre-Yves David authored
-
Pierre-Yves David authored
-
Pierre-Yves David authored
The computation of impacted nodes and associated revs is fully reworked. In addition,we introduce multiple new tests covering cases that were previous wrongly handled.
-
Pierre-Yves David authored
We are about to update the logic and add more tests.
-
Pierre-Yves David authored
Before this changesets, parent of standard obsmarkers were wrongly considered affected and pruned changeset were wrongly not considered affected.
-
Pierre-Yves David authored
It is a fast way to know we don't have an affected range for an affected revision.
-
Pierre-Yves David authored
Before this changeset we where resetting in all cases, and then looking for affected ranges. In addition is the stable range were not available, the functions silently returned no ranges affected. Now, do one or the other depending of the availability of the stable range cache. In practice we always do a broad reset because the code detecting affected changeset is currently buggy.
-
Pierre-Yves David authored
The new way make me a bit less sad than the old one.
-
Pierre-Yves David authored
Otherwise we may end up in situation were cache are not warmed in the right order, crashing.
-
Pierre-Yves David authored
-
Pierre-Yves David authored
-
Pierre-Yves David authored
We were using the wrong variable.
-
Pierre-Yves David authored
There are no reason to use a list here.
-
- Aug 08, 2018
-
-
Yuya Nishihara authored
The extension version uses old API, which will be deprecated in Mercurial 4.8.
-
- Aug 13, 2018
-
-
Pierre-Yves David authored
This avoid confusion when installing non-tagged version.
-
- Aug 03, 2018
-
-
Pierre-Yves David authored
-
- Aug 02, 2018
-
-
Boris Feld authored
Due to the way of how successor sets are retrieved in new Mercurial version, retrieving it again in 4.3 way would be a performance hit and complexify the code too much. Don't retrieve markers of successor sets which makes obslog filtered output more limited in 4.3.
-
Pulkit Goyal authored
In hg<=4.3, copies._fullcopytracing() does not exist and we have to wrap copies.mergecopies() to fix the AssertionError coming from core.
-