- Oct 02, 2018
-
-
Matt Harbison authored
I missed these in 803b7569c9ea because I forgot about `...` lines.
-
Matt Harbison authored
-
Matt Harbison authored
This is needed to keep py3 happy. The other two instances of sorting already did this.
-
Matt Harbison authored
There's still a stacktrace about not being able to serialize _io.TextIOWrapper.
-
Matt Harbison authored
-
- Oct 01, 2018
-
-
Matt Harbison authored
-
- Jun 22, 2018
-
-
Martin von Zweigbergk authored
By inlining it, we also avoid calculating the value when "if of in seen" is false (probably not significant). Differential Revision: https://phab.mercurial-scm.org/D4831
-
- Sep 16, 2018
-
-
Martin von Zweigbergk authored
"parentrepo" and "repo" were the same thing and I don't see much reason for it (unionrepo has similar structure and a similar alias but there are two repos there so at least it makes a little more sense there). Differential Revision: https://phab.mercurial-scm.org/D4830
-
- Oct 01, 2018
-
-
Augie Fackler authored
-
durin42 authored
-
durin42 authored
-
- Sep 05, 2018
-
-
Yuya Nishihara authored
Spotted by ASAN.
-
Yuya Nishihara authored
Even though the entire manifest data should be terminated by '\0', it seems not nice to scan '\0' over the entry terminator, '\n'.
-
- Sep 28, 2018
-
-
Martin von Zweigbergk authored
Differential Revision: https://phab.mercurial-scm.org/D4824
-
Martin von Zweigbergk authored
The patch overrides became unnecessary when I made context.status() filter by the narrowspec in e411774a2e0f (narrow: move status-filtering to core and to ctx, 2018-08-02). Differential Revision: https://phab.mercurial-scm.org/D4823
-
Martin von Zweigbergk authored
We had a test that shows that trying to explicitly add a file outside the narrowspec results in an error, but we didn't have a test that shows that paths from subdirectories outside the narrowspec are not added (on e.g. `hg add .`) but silently ignored. Differential Revision: https://phab.mercurial-scm.org/D4822
-
- Oct 01, 2018
-
-
Augie Fackler authored
Differential Revision: https://phab.mercurial-scm.org/D4818
-
- Sep 29, 2018
-
-
Pulkit Goyal authored
This will be used in core logic to determining whether a server is ellipses enabled or not. And also this will ease moving narrow related things to core. Differential Revision: https://phab.mercurial-scm.org/D4809
-
Pulkit Goyal authored
We are trying to integrate the whole of narrow logic into core and it will be helpful for upcoming patches to have these capability names in core. The next patch will move the ellipses capability to core also. The exact motivation is to know whether we are cloning a ellipses repo or not and adding an ellipses repo requirement. Differential Revision: https://phab.mercurial-scm.org/D4808
-
- Sep 30, 2018
-
-
Yuya Nishihara authored
-
Yuya Nishihara authored
I think it's good enough to stabilize the feature, at least for the core and non-experimental commands.
-
Yuya Nishihara authored
-
Yuya Nishihara authored
I think {lineno} looks more like a common template keyword. It isn't called a {line} to avoid conflicts with the element name of {lines} and the {_|splitlines} filter. https://www.mercurial-scm.org/wiki/GenericTemplatingPlan#Dictionary
-
Yuya Nishihara authored
This is a part of the name unification. I think it's somewhat useful to provide a combined view of change/merge statuses. https://www.mercurial-scm.org/wiki/GenericTemplatingPlan#Dictionary
-
- Oct 01, 2018
-
-
Augie Fackler authored
Differential Revision: https://phab.mercurial-scm.org/D4817
-
- Nov 03, 2017
-
-
Boris Feld authored
We detected that pager is waiting for log-to-process script to finish, which is annoying when adding a script on commandfinish that does an HTTP push. There seems to be no workaround on the script side and it will make the behavior on Linux/MacOS closer to the Windows behavior. The drawback is that it makes the related tests more flaky as log-to-process outputs are now really asynchronous. If it's considered a BC change, another option would be to add a config option for this new behavior. I personally think that the different behavior between Windows and Linux is confusing and that it's a bug I would be fine with a new config option. Differential Revision: https://phab.mercurial-scm.org/D4816
-
Boris Feld authored
The next changeset will fix the bad interaction between the pager and log-to- process. Add a test first to make the next changeset easier to understand. Differential Revision: https://phab.mercurial-scm.org/D4815
-
- Sep 30, 2018
-
-
Pulkit Goyal authored
Thanks to Matt Harbison who fixed the remaining failures of this test. Differential Revision: https://phab.mercurial-scm.org/D4814
-
- Sep 27, 2018
-
-
Boris Feld authored
-
- Sep 22, 2018
-
-
Boris Feld authored
The logic for this change is similar to the change to `cleanupnodes` that we did earlier. Now that the rebase code is trying to record a fold, we need to actually record it in the markers. The first step is to have the markers creation API able to receive such fold data. To keep things sane, we restrict fold to on successors.
-
- Sep 26, 2018
-
-
Boris Feld authored
This will help to make the next change clearer.
-
Boris Feld authored
To track folds, we are about to change the content of `rel`. To simplify this change, we update the `geteffectflag` function beforehand.
-
Boris Feld authored
A collapse is a large fold. It is now explicitly tracked (at the cleanupnodes API level).
-
Boris Feld authored
Now that `cleanupnodes` support tuples as key, we update the rebase code to use them. No changes in the replacement tracked are introduced yet.
-
Boris Feld authored
When a one-liner gets 3 lines longs, it lose its expressivity benefits. We expand it into a simple for loop. This makes future changes of the code in that area clearer.
-
Boris Feld authored
The `cleanupnodes` has logic to skip the creation of "prune" markers if the changeset is already obsolete. This feels strange and gets in the way of code changes to tracks folds. Now that callers no longer request such prune, we can drop this logic. In many cases, pruning through cleanupnodes should be replaced by internal phase usage.
-
Boris Feld authored
With similar motivations to the previous changesets, we stop marking changeset from pruning when it is not the command intention. In this case, we still need to distinguish between the strip and the obsolete case.
-
Boris Feld authored
If something else took care of these temporary nodes, we don't need to do anything about it. This less liberal usage of pruning through cleanup nodes will help us further cleanup on the road to explicitly tracks folds.
-
- Sep 30, 2018
-
-
Matt Harbison authored
I couldn't figure out how to get the list to print without b'' with pycompat.write(), without converted each element to str.
-
Matt Harbison authored
I *think* this is the last of them.
-