- 23 Dec, 2020 1 commit
-
-
Pierre-Yves David authored
The context method might be wrapped without topic being installer. So we need to deal with that case. This might happen in some case where topic is loaded but not enabled (eg: two repository in the same process).
-
- 11 Jan, 2021 1 commit
-
-
Anton Shestakov authored
-
- 10 Jan, 2021 2 commits
-
-
Anton Shestakov authored
Makes it easier to do e.g. debugging in functions that uses `node` as a variable name. For the record, variable named `node` is used 5 times in this file. mercurial.node module is used in 4 cases seen in this patch and 2 of them already can be written without using `node` (nullid is imported directly).
-
Anton Shestakov authored
-
- 30 Oct, 2020 3 commits
-
-
Martin von Zweigbergk authored
-
Martin von Zweigbergk authored
-
Martin von Zweigbergk authored
Mercurial has a new `command-templates.oneline-summary` config that is respected by `hg rebase`, `hg phabsend`, and the bundled version of `hg split`. This patch makes `hg evolve` also respect it. Unlike the upstream commands, I let `hg evolve` use the existing template by default. The reason I didn't change the default is that we have a different template when topics are enabled and it's unclear how that should work with the default from upstream. So at least for now, the user will have to explicitly set the new config if they want it to apply to `hg evolve`.
-
- 29 Oct, 2020 2 commits
-
-
Martin von Zweigbergk authored
We only depend on its `.show(ctx)` function, so it's enough to pass around that function instead. That will make it easier to replace the function by another one in a later patch.
-
Martin von Zweigbergk authored
The variable is reassigned just a few lines later.
-
- 15 Oct, 2020 1 commit
-
-
Martin von Zweigbergk authored
It seems to have been unnecessary for at least five years.
-
- 30 Nov, 2020 2 commits
-
-
Sushil Khanchi authored
Before this patch, if repo.branchheads() were asked to return heads of a branch and if there is any active topic, it would append that topic name to branch name and search heads for it and return wrong results. Because of this behavior we get wrong results for "hg heads" command because, this command make a list of heads of each branch in branchmap. So if wdir parent has an active topic, it would search for "branch:topic" instead of "branch" for each branch. Now we append topic only when branch is not passed to the function. Changes in test-topic.t file reflect the fixed behavior. Changes in test-topic-stack-data.t are obvious but not correct for `hg sum` output, which is because that's what the expected behavior acc. to the current logic in `hg sum` as it looks for the heads of branch of wdir parent and calculate new commits like this: new = ancestor(all branch heads) - ancestor(current parent) So, it doesn't really care if wdir parent has a topic which is why we are getting wrong result for "update:" in `hg sum`. You might be wondering why it was returning the correct output before, but I digged into it and can tell you that it's just a false combination of current cset and code bits which gave the correct results. If we want to correctly fix the issue we probably need to wrap `hg sum` command.
-
Sushil Khanchi authored
Being on an active topic change the result of `hg heads`, as demonstrated in added test. This will be fixed in next patch.
-
- 23 Dec, 2020 4 commits
-
-
Pierre-Yves David authored
Right now, this introduce a bug… however this will prevent the next changesets to break the computation for "how many other changeset on that branch". That last remaining bug (introduced in this series) seems a lesser evil.
-
Pierre-Yves David authored
`hg summary` will do some comparison between the current branch and the parents branch, so we need that covered too.
-
Pierre-Yves David authored
We will need it for `hg summary`, so we start by making it its own context manager.
-
Anton Shestakov authored
CORE-TEST-OUTPUT-UPDATE: 9261f6c1d39b
-
- 16 Dec, 2020 1 commit
-
-
Pierre-Yves David authored
-
- 13 Dec, 2020 1 commit
-
-
Pierre-Yves David authored
Right now reading topic information twice means we uncompress a full revision twice. On a simple `hg topic --age` in my mercurial clone, the total runtime goes from 40s to 10s. Still too slow, but significantly less.
-
- 01 Dec, 2020 1 commit
-
-
Georges Racinet authored
We move the branch name retrieval after the early continue: it was not needed before. On my PyPy clone, this saves about 1.4ms in the time to run _filter_obsolete_heads() for the branchmap entries of the default branch. PyPy having lots of closed branches, for the complete analysis that Heptapod currently performs on each push for PyPy, this gains around 100ms (2.5% for a total time around 4s). All those figures on my workstation.
-
- 13 Dec, 2020 1 commit
-
-
Martin von Zweigbergk authored
4d5e2fd53707 (singlehead: introduce option to restrict to public changes, 2020-12-05) added a new argument (`filtername`) to the signature. This patch makes us compatible with that.
-
- 08 Dec, 2020 1 commit
-
-
Anton Shestakov authored
The test case explicitly uses fake-editor.sh with sleep 5 to test that hg prev and hg next both lock working directory properly. But recent upstream tweak in run-tests.py sets this timeout to 15, which is too high for this test. Let's set it back to its default value of 0.
-
- 02 Dec, 2020 3 commits
-
-
Anton Shestakov authored
CORE-TEST-OUTPUT-UPDATE: fc4fb2f17dd4
-
Anton Shestakov authored
CORE-TEST-OUTPUT-UPDATE: fa87536d3d70
-
Anton Shestakov authored
CORE-TEST-OUTPUT-UPDATE: 95c4cca641f6 CORE-TEST-OUTPUT-UPDATE: 50afeeeb7b79 CORE-TEST-OUTPUT-UPDATE: 122f0b59f5f0 CORE-TEST-OUTPUT-UPDATE: ca39c45014fa
-
- 27 Nov, 2020 1 commit
-
-
Anton Shestakov authored
marmoute decided to drop it because it's "neither documented nor a good idea". This extensions was assemble to deal with Facebook willingness to check `hg strip` semantic for its user. Changing `hg strip` semantic is overall a pretty bad idea, because `stripping` is a specific operation, that is problematic in distributed version control but have a narrow set of valid usecase (eg: maintenance). Diverting user away from `prune` in favor of a modified `strip` is a bad idea, because it mask the legitimate `strip` usage and introduce confusion in user heads, The verb is not appropriate and the behavior of `prunestrip` does not match the one of vanillia `strip`. Facebook is no longer using this, and the lack of documentation is a good hint that nobody else is. So lets drop it.
-
- 26 Nov, 2020 3 commits
-
-
Pierre-Yves David authored
-
Anton Shestakov authored
CORE-TEST-OUTPUT-UPDATE: ac362d5a7893
-
Anton Shestakov authored
Now that strip lives in core hg, let's test that using debugstrip without enabling strip extension works as expected.
-
- 25 Nov, 2020 1 commit
-
-
Anton Shestakov authored
Since the debugstrip command from core and strip command from the hgext.strip extension is now the same thing, we don't have to wrap them separately. Unless, of course, users have a copy of old (from hg 5.6 and earlier) hgext.strip laying around that they specifically want to use, but I don't think we want to support that use case.
-
- 23 Nov, 2020 1 commit
-
-
Anton Shestakov authored
--HG-- branch : stable
-
- 20 Nov, 2020 2 commits
-
-
Georges Racinet authored
The location is perhaps more debatable, but it is now also available there. --HG-- branch : stable
-
Georges Racinet authored
Primary motivation is rate limiting on Docker Hub --HG-- branch : stable
-
- 19 Nov, 2020 1 commit
-
-
Martin von Zweigbergk authored
CORE-TEST-OUTPUT-UPDATE: 21733e8c924f CORE-TEST-OUTPUT-UPDATE: 8d72e29ad1e0 CORE-TEST-OUTPUT-UPDATE: e0dbfbd4062c CORE-TEST-OUTPUT-UPDATE: ebee234d952a CORE-TEST-OUTPUT-UPDATE: 527ce85c2e60 CORE-TEST-OUTPUT-UPDATE: 3175b0e0058b CORE-TEST-OUTPUT-UPDATE: f96fa4de5055 CORE-TEST-OUTPUT-UPDATE: 96ca817ec192
-
- 16 Nov, 2020 1 commit
-
-
Martin von Zweigbergk authored
`cmdutil.commitstatus()` was changed in https://phab.mercurial-scm.org/D9257 so it has a new `tip` argument. This patch adds compatibility with that. It was harder than I expected because the callers all pass the arguments as positional, so we can't look for `opts` or `tip` in the `kwargs`. I instead extracted much of the override to a helper. I think the result is okay.
-
- 11 Nov, 2020 1 commit
-
-
Anton Shestakov authored
--HG-- branch : stable
-
- 29 Oct, 2020 1 commit
-
-
Martin von Zweigbergk authored
CORE-TEST-OUTPUT-UPDATE: e9555305c5c6
-
- 31 Oct, 2020 4 commits
-
-
Pierre-Yves David authored
-
Pierre-Yves David authored
--HG-- branch : stable
-
Anton Shestakov authored
--HG-- branch : stable
-
Anton Shestakov authored
--HG-- branch : stable
-