- Oct 02, 2018
-
-
Sushil Khanchi authored
As repository grows revision number lose their usefulness. To make it a little better than now, after this patch we will be using short stack aliases introduced by the topic extension (as displayed by `hg stack`). These stack aliases s# will be used only when user has enabled topic extension and his repo's current active topic is same as the revs to be evolved. For now, this patch doesn't cover `continue` case. I will discuss about this with Pierre-Yves David. Maybe we have to store the info in evolvestate that "we were using stack aliases".
-
- Oct 01, 2018
-
-
Sushil Khanchi authored
I extracted this displayer method to _solveone() so that it would be easy to pass a different template to show evolve msgs. In upcoming patches we will be using stacktemplate in some cases where we want to include stack alias s# in evolve msgs.
-
Sushil Khanchi authored
This template use stack alias s# instead of rev number in messages printed when we run `hg evolve`. For example, this template's msgs will look like this: move:[s3] add aaa atop:[s2] add bbb move:[s4] add ccc I will be using this template in upcoming patches.
-
Sushil Khanchi authored
This keyword will be useful where we want to see the index of the changeset in the stack when we run `hg stack`.
-
- Oct 09, 2018
-
-
Pierre-Yves David authored
-
- Oct 02, 2018
-
-
Pulkit Goyal authored
Yuya stabilized the -T option and now it's in help by default. CORE-TEST-OUTPUT-UPDATE: 0d703063d0c8
-
- Sep 26, 2018
-
-
Pierre-Yves David authored
-
Pierre-Yves David authored
There were still case where a range was issued too early.
-
Pierre-Yves David authored
We use node order to make this repeatable from one clone to another. This is an arbitrary pick.
-
Pierre-Yves David authored
previous, we dealt with the case where the tippest subrange of the stable parent was too long. Now, we need to deal with the case where it is too small.
-
Pierre-Yves David authored
-
- Sep 25, 2018
-
-
Pierre-Yves David authored
This also adds a way to skip "caching" smaller range in the debugcommand (not in the extensions itself).
-
Pierre-Yves David authored
-
Pierre-Yves David authored
This new command should help checking that the stable range produce reusable bundle.
-
Pierre-Yves David authored
Right now, we don't have a reliable progress report when using pullbundle.
-
Pierre-Yves David authored
-
Pierre-Yves David authored
Otherwise we can end-up with a too many file open at the same time.
-
Pierre-Yves David authored
The previous method could get confuse by merge and overslice. The new method is better at using sticking on power of two boundaries.
-
Pierre-Yves David authored
Pull bundle trigger slicing from range with arbitrary initial skip. We have to adjust the current slicing to take this into account.
-
- Sep 23, 2018
-
-
Pierre-Yves David authored
Since we do not serve the full repository, we use more stablerange starting from a random point. These are probably not loaded yet and should be cached. This is best effort caching, if we can't save them we won't.
-
Pierre-Yves David authored
-
Pierre-Yves David authored
-
Pierre-Yves David authored
This will be useful to monitor overall performance.
-
Pierre-Yves David authored
-
Pierre-Yves David authored
We issue a single final pull, most of its item are reusable.
-
- Sep 22, 2018
-
-
Pierre-Yves David authored
We now only generate a bundle once (and store it to disk). If we need it again, we use it directly from disk.
-
- Sep 23, 2018
-
-
Pierre-Yves David authored
We subdivide the set of missing revisions into multiple "range" using the "stable range" data structure. This slicing aims at maximizing the capability of the resulting ranges.
-
Pierre-Yves David authored
Right now, we do not do any slicing, but we install the wrapping and the tests.
-
- Sep 21, 2018
-
-
Pierre-Yves David authored
CORE-TEST-OUTPUT-UPDATE: 4bd6e444c76f
-
Pierre-Yves David authored
-
- Sep 22, 2018
-
-
Pierre-Yves David authored
Mercurial's core changeset: 6c8ceebce309 revealed an issue. If the creator of a workingcommitctx explicitly assigned a 'topic', it was silently overridden by the current active on. This break import of patch with topic information. We now respect preexisting topic information.
-
- Sep 21, 2018
-
-
Pierre-Yves David authored
The attribute was made private in 4024c363cd33.
-
Pierre-Yves David authored
The attribute was made private in ebbba3ba3f66.
-
Sushil Khanchi authored
Copying the discription of this redundancy issue given by Pierre Yves David: When running `hg evolve` to stabilize orphan changeset output about the currently stabilized changeset is issued. For example: $ hg evolve move:[3] a3 atop:[4] a2 working directory is now at 7c5649f73d11 This output can become quite repetitive when orphan are stabilized atop each other. For example: $ hg evolve --all move:[8] dansk 2! atop:[10] dansk! merging main-file-1 move:[9] dansk 3! atop:[11] dansk 2! In this case it would be smoother to issue: $ hg evolve --all move:[8] dansk 2! atop:[10] dansk! merging main-file-1 move:[9] dansk 3! Since we are moving "dansk 3!" atop the changeset we just stabilized. When adding this be careful that we still want to issue the "atop" message in various cases: 1. first changesets in a stack 2. when the orphan is not stabilized atop previous one 3. when using hg evolve --continue to resume an evolution So, I have made the changes which also respect above listed three points. And changes in tests/test-evovle*.t reflecting the changed behavior.
-
Pierre-Yves David authored
The `tr` object can be None.
-
- Sep 18, 2018
-
-
Pierre-Yves David authored
-
- Sep 17, 2018
-
-
Gregory Szorc authored
Upstream commits 71d83b315778 and abce899c985f changed the calling convention of setdiscovery._takefullsample(). We inspect the signature of the function before calling it so we can pass the proper arguments.
-
- Sep 14, 2018
-
-
Pierre-Yves David authored
-
Pierre-Yves David authored
This avoid confusion when people install version from source.
-
Pierre-Yves David authored
-