- Sep 29, 2019
-
-
Gregory Szorc authored
Otherwise the source transformer converts it to bytes and test-check-interfaces.py complains on Python 3. Differential Revision: https://phab.mercurial-scm.org/D6919
-
Gregory Szorc authored
Otherwise it is printed and the test fails with tons of output on Python 3. Differential Revision: https://phab.mercurial-scm.org/D6918
-
Gregory Szorc authored
The wording has been tweaked in new versions of pip. Differential Revision: https://phab.mercurial-scm.org/D6909
-
Gregory Szorc authored
This prevents the sub test harness from rebuilding Mercurial. It shaves ~30s from the test wall time on my machine. Differential Revision: https://phab.mercurial-scm.org/D6908
-
Gregory Szorc authored
This silences some test-check-pyflakes.t warnings on Python 3. Differential Revision: https://phab.mercurial-scm.org/D6907
-
- Sep 26, 2019
-
-
Pierre-Yves David authored
Some conditional were missing.
-
- Sep 27, 2019
-
-
Pierre-Yves David authored
Oops, we forgot to register data file when blanky copying revlog. Now that we are actually copying these `.d` files, we should also register them. Differential Revision: https://phab.mercurial-scm.org/D6905
-
Pierre-Yves David authored
The test did not used any `.d` file. So of course, their handling was broken (for vfs encoding reason again). We fix the issue and update the test. Note that some fncache issue remains with `.d` file. It will be taken care of in the next changesets. Differential Revision: https://phab.mercurial-scm.org/D6904
-
Pierre-Yves David authored
Differential Revision: https://phab.mercurial-scm.org/D6903
-
Pierre-Yves David authored
The encoding in vfs mess up with the directory we are trying to create manually. We could duplicate the advanced logic some more, but that seems ill fated. Instead, we let the vfs deal with directory creation. We update the test to contains a name affected by encoding. Differential Revision: https://phab.mercurial-scm.org/D6902
-
Pierre-Yves David authored
If we do a full addition, we need to start from the full text. Differential Revision: https://phab.mercurial-scm.org/D6901
-
Pierre-Yves David authored
The documentation of the `debugupgraderepo` command was updated when `re-delta-fulladd` was introduced. However, the docstring of the `revlog.clone` method was not. Differential Revision: https://phab.mercurial-scm.org/D6900
-
Pierre-Yves David authored
The content of the clone method now focus on parameters validation and processing. The `_clone` method focus on the actual cloning logic. Splitting the method out save some indentation and clarify each method code since it a focussed on one goal. Differential Revision: https://phab.mercurial-scm.org/D6899
-
- Sep 06, 2019
-
-
Pierre-Yves David authored
It became an empty shell. Differential Revision: https://phab.mercurial-scm.org/D6823
-
Pierre-Yves David authored
This is a small duplication, and the last bit we need to get rid of the mixin. Honestly, I am not fan of that class attribute and it mostly exist to accomodate The simple-storage whose usage of flag processors is dumbious and that is currently dead code anyway. However I don't want to be pulled into futher unrelated cleaning so it is a small price to pay. Differential Revision: https://phab.mercurial-scm.org/D6822
-
Pierre-Yves David authored
The code duplication benign and will get removed in a couple of month anyway. Differential Revision: https://phab.mercurial-scm.org/D6821
-
Pierre-Yves David authored
One more steps toward removing the mixin. Differential Revision: https://phab.mercurial-scm.org/D6820
-
Pierre-Yves David authored
One more steps toward removing the mixin. Differential Revision: https://phab.mercurial-scm.org/D6819
-
Pierre-Yves David authored
One more step towards removing the mixin. Differential Revision: https://phab.mercurial-scm.org/D6818
-
Pierre-Yves David authored
This is the first step toward removing the flag processing mixin. Differential Revision: https://phab.mercurial-scm.org/D6817
-
- Sep 03, 2019
-
-
Pierre-Yves David authored
If we want some flag processors to be able to store sidedata it needs to be actually fed that data. Differential Revision: https://phab.mercurial-scm.org/D6816
-
Pierre-Yves David authored
To read sidedata using flagprocessors, we need flag processors to store them. So we pass this information to the flag processing layer. Differential Revision: https://phab.mercurial-scm.org/D6815
-
Pierre-Yves David authored
If we want to eventually store sidedata we need to be able to pass them along. Differential Revision: https://phab.mercurial-scm.org/D6814
-
Pierre-Yves David authored
This makes it possible for flag processors to -read- flag data. Differential Revision: https://phab.mercurial-scm.org/D6813
-
Pierre-Yves David authored
This function input and return are becoming stranger and stranger bnut I don't have a good plan to make is saner without problematic code duplication, so it will be this way to now. Differential Revision: https://phab.mercurial-scm.org/D6812
-
Pierre-Yves David authored
Right now, flag processors does not return sidedata, by they will. So, we prepare the caller to receive it. Differential Revision: https://phab.mercurial-scm.org/D6811
-
Pierre-Yves David authored
So far things, seems logical. Differential Revision: https://phab.mercurial-scm.org/D6810
-
Pierre-Yves David authored
Nothing extra any side data yet. However, it will happens in the future. So we better prepare the callers of the `_revisiondata` to deal with it. Differential Revision: https://phab.mercurial-scm.org/D6809
-
Pierre-Yves David authored
The method give access to extra information related to the revision. Such data will not be part of the hash be strongly related to the revision. Having them stored at the revlog level helps the storage consistency story and simplify various things. Example of data we could store there: - copy tracing related informations - graph structure related information (useful for discovery) - unresolved conflict data The full implementation will be introduced gradually in the coming changesets. Differential Revision: https://phab.mercurial-scm.org/D6808
-
- Sep 25, 2019
-
-
Martin von Zweigbergk authored
merge.calculateupdate() takes a lot of parameters and I get confused all the time which is which. See also b14fdf1fb615 (update: clarify update() call sites by specifying argument names, 2017-02-09). Differential Revision: https://phab.mercurial-scm.org/D6883
-
Augie Fackler authored
All the callsites of this method have access to the repo, and I'd rather not have to duplicate this across alternative bmstore implementations. Besides, it feels like a bit of a layering violation. .. api:: `mercurial.bookmarks.bmstore` no longer has a convenience method for looking up changectx instances from a bookmark name. Use `repo[repo.bookmarks[name]]` intead of `repo.bookmarks.changectx(name)`. Differential Revision: https://phab.mercurial-scm.org/D6884
-
Augie Fackler authored
This bug is as old as histedit, which is more than 10 years! I'm a little sad about the extra calculations here that we're just going to throw out, but I don't see any better way to look for untracked file conflicts and I want the bug fixed. Differential Revision: https://phab.mercurial-scm.org/D6882
-
- Sep 23, 2019
-
-
Augie Fackler authored
I'm honestly impressed that nobody has hit this in the over a decade that histedit has existed, but here we are. Differential Revision: https://phab.mercurial-scm.org/D6881
-
- Sep 25, 2019
-
-
Paul Gossman authored
When --keep is passed with rebase, the new nodes created are not accessible from templates. This change enables accessing the newly-created nodes from nodechanges, just as if --keep was not set. Differential Revision: https://phab.mercurial-scm.org/D6880
-
- Sep 21, 2019
-
-
Matt Harbison authored
Differential Revision: https://phab.mercurial-scm.org/D6874
-
- Sep 25, 2019
-
-
Matt Harbison authored
Differential Revision: https://phab.mercurial-scm.org/D6875
-
Augie Fackler authored
This shouldn't make any difference for legal code, but it'll prevent the assertion from being optimized out if someone decides to do -O on our code. Differential Revision: https://phab.mercurial-scm.org/D6879
-
Augie Fackler authored
.. api:: `mercurial.hg.updatetotally` is now more thorough about checking its `updatecheck` keyword argument. Previously invalid values would have used the configured default updatecheck method, but now will raise ValueError. Differential Revision: https://phab.mercurial-scm.org/D6878
-
Augie Fackler authored
.. api:: `mercurial.hg.update*` and `mercurial.merge.update` now expect a value from a set of NAMED_CONSTANTS (`merge.UPDATECHECK_*` constants) rather than a collection of magic strings. As of now, the values are the same, but code should be prepared for these values to change in the future. Differential Revision: https://phab.mercurial-scm.org/D6877
-
Pierre-Yves David authored
Until now, the experimental option `single-head-per-branch` was also refusing closed heads. The logic is now ignoring them by default and a suboption have been added to refuse them too `single-head-per-branch:account-closed-heads`.
-