- Sep 29, 2018
-
-
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.
-
Matt Harbison authored
-
Matt Harbison authored
This makes test-doctest.py happy on Windows.
-
Matt Harbison authored
With py3 on Windows, the prompt to accept changes in an --interactive run wasn't showing up until after the choice was read from stdin.
-
Pulkit Goyal authored
This makes the python 3 buildbot green again. Differential Revision: https://phab.mercurial-scm.org/D4811
-
- Sep 27, 2018
-
-
Martin von Zweigbergk authored
It has been a programming error to pass a 40-character string that is not a hex nodeid since 8b86acc7aa64 (context: drop support for looking up context by ambiguous changeid (API), 2018-04-28), so we can just let it raise a TypeError. Differential Revision: https://phab.mercurial-scm.org/D4807
-
Martin von Zweigbergk authored
FilteredRepoLookupError is only raised by changectx's constructor and the higher-level scmutil.revsymbol(), so there's no need to catch it in changectx's constructor. Differential Revision: https://phab.mercurial-scm.org/D4806
-
- Sep 29, 2018
-
-
Matt Harbison authored
-
- Sep 26, 2018
-
-
Matt Harbison authored
Windows insisted that it needs to be str. I skipped the stuff in the posix module, and left `tests/f` and `run-tests.py` alone for now.
-
- Sep 29, 2018
-
-
Matt Harbison authored
-
Matt Harbison authored
-
Matt Harbison authored
-
- Sep 27, 2018
-
-
Boris Feld authored
If we already have some obsolete and hidden nodes locally and the server send them again to you, it seems useful to point it out instead of being silent about it.
-
Boris Feld authored
Changeset pulled from a remote repository while already obsolete locally can end up hidden after the pull. Hiding obsolete changesets is a good behavior but silently "skipping" some of the pulled content can get confusing. We now detect this situation and emit a message about it. The message is simple and the wording could be improved, however, we focus on the detection here. Evolution is still an experimental feature, so the output is open to changes. In particular, we could point out at the latest successors of the obsolete changesets, however, it can get tricky is there are many of them. So we delay these improvements to another adventure. Another easy improvement would be to merge this message with the previous line about the new nodes and their phases. This is a good example of cases where we can only transmit a limited amount of data to users by default. We need some sort of "transaction journal" we could point the user to.
-
Boris Feld authored
We are about to add more logic in this report. Before that, we need it to not quit so early.
-
Boris Feld authored
Obsolescence is closely related to visibility but still a distinct concept. We can receive changesets that are obsolete but visible (eg: when pulling orphans). Such changeset should be reported too. In addition, the filtering level can be anything, we should respect it.
-
Boris Feld authored
The current code ignores all obsolete changesets including the visible one. We add a test showing this behavior before fixing the behavior.
-
- Sep 26, 2018
-
-
Martin von Zweigbergk authored
We were doing repo['tip'].node() or similar in a few places where repo.changelog.tip() would be enough. Differential Revision: https://phab.mercurial-scm.org/D4781
-
- Sep 27, 2018
-
-
Martin von Zweigbergk authored
I think lookup of the 'null' symbol should be done via scmutil.revsymbol() and repo['null'] is only supported for historical reasons. However, repo[nullrev] is fine, so we can switch to that instead of switching to scmutil.revsymbol('null'). Differential Revision: https://phab.mercurial-scm.org/D4780
-