- Feb 17, 2025
-
-
Raphaël Gomès authored
This was missed in 0bd91b0a1a93. It still works because we haven't removed the `hg-cpython` bridge yet. I'm honestly not sure if we should continue advertising for fsmonitor at all with the Rust extensions, but that's another discussion.
-
- Feb 18, 2025
-
-
Pierre-Yves David authored
The current choice is the default so nothing is changing there, but we document why we cannot use something else.
-
Pierre-Yves David authored
When we moved to use setuptools-scm in 30510238284e, we lost the version scheme that was engineers to make it safe to produce and consume nightly build from multiple branches (stable, default, and privates branches). This small change give use something close to what we have, but still don't support multiple branch.
-
- Feb 19, 2025
-
-
Pierre-Yves David authored
Windows need an additional flag to open the file properly.
-
- Feb 18, 2025
-
-
Pierre-Yves David authored
This argument have been around for a while and simplify the code. This is especially true as Windows does not have `os.fchmod` so we would have had to deal with this special case.
-
- Feb 07, 2025
-
-
Mitchell Kember authored
This adds support to rhg annotate for all the whitespace options: -w, --ignore-all-space -b, --ignore-space-change -B, --ignore-blank-lines -Z, --ignore-space-at-eol Note that --ignore-blank-lines has no effect on annotate so it is ignored. You can see this in dagop.py _annotepair which only checks if blocks are '=' or not, whereas the effect of --ignore-blank-lines is to change some '!' into '~'. When the other 3 are combined, we use the strongest option since -w implies -b and -b implies -Z. This is not explicit in the Python implementation, but I have verified that's how it behaves.
-
- Feb 12, 2025
-
-
Mitchell Kember authored
This was missing from the whitespace option testing in test-annotate.t. I changed the "a" file contents a bit to make the output different from the other whitespace flags.
-
- Feb 18, 2025
-
-
Pierre-Yves David authored
All other call site were going to go through this specific function anyway, so lets rationalize the use of this function.
-
Pierre-Yves David authored
This new form should hopefully be clearer and less error prone.
-
Pierre-Yves David authored
-
Pierre-Yves David authored
The code was calling `_set_identity` in too many places, resulting in fetching cache information after reading the on disk data. This could result in old data labelled with the identity of new, never loaded data. Fixing it solve the issue spotted in the previous changesets. Further cleanup are warranted but it seems more reasonable to do them on stable.
-
Pierre-Yves David authored
This was giving the wrong output in the `dirstate-v2-rewrite` case. As the dirstate is rewritten, the data file is missing and we reload the full dirstate. The make the dirstate reloaded after the commit and it no longer see the file as dirty. Note that if we were deleting the data file less aggressively, we would see the other output. (for example if we were keeping old data file around for some time before deletion). One last thing… fixing this reveal a quite serious bug where a `hg status` end up overwriting a `hg update` done concurrently. Hooray for proper testing.
-
Pierre-Yves David authored
`#if dirstate-v2` is always false, because `dirstate-v2` is not one of the test cases. So we fix the conditionnal and adjust the expected matching. This highlight that the rhg/no-rhg output differ because an issue in the code. We will fix that in the next changeset.
-
Pierre-Yves David authored
We are going to fix a bug in the test framework, that will reveal a fairly serious bug with the Rust code. So we update the test before hand for clarity.
-
Julien Cristau authored
stream bundle specs specify requirements, but we were ignoring this when selecting which bundle to apply, causing spurious clone failures.
-
Pierre-Yves David authored
That target no longer pre-built thing in place to prepare artifact to be used by `make install`. So using the same logic as in 037febb862d2 and drop the target instead of keeping something surprising / useless.
-
- Feb 17, 2025
-
-
Pierre-Yves David authored
We are using the wrong name.
-
- Feb 11, 2025
-
-
Mathias De Mare authored
-
Mathias De Mare authored
-
Mathias De Mare authored
-
Mathias De Mare authored
-
- Feb 06, 2025
-
-
Mathias De Mare authored
-
- Feb 04, 2025
-
-
Mathias De Mare authored
-
Mathias De Mare authored
-
Mathias De Mare authored
-
- Feb 03, 2025
-
-
Mathias De Mare authored
-
Mathias De Mare authored
-
- Feb 04, 2025
-
-
Mathias De Mare authored
-
- Feb 03, 2025
-
-
Mathias De Mare authored
This is useful when trying to run docker builds with host platforms that cannot build a recent hg (for example RHEL8 and derivatives).
-
Mathias De Mare authored
-
- Feb 18, 2025
-
-
Pierre Augier authored
The Makefile is now usable by Mercurial developers and for downstream packaging. `make help` explains how. I had to introduce more options (PIP_OPTIONS_INSTALL, PIP_PREFIX) to be able to change the behavior of the install targets (usable for local installation and downstream packaging) and to deal with an issue on Linux with the --prefix pip option (see https://discuss.python.org/t/linux-distro-patches-to-sysconfig-are-changing-pip-install-prefix-outside-virtual-environments/18240).
-
Pierre Augier authored
It is useless now and its presence could be misunderstood. People using it will get an error, run `make help` and adapt their code.
-
Pierre Augier authored
-
Pierre Augier authored
-
Pierre Augier authored
-
- Feb 04, 2025
-
-
Pierre Augier authored
-
- Feb 17, 2025
-
-
Pierre-Yves David authored
This is in line with the current project goal. (do we need a `dist-notest` target at all?)
-
Pierre-Yves David authored
This is in line with the current project goal. (do we need a `wheel` target at all?)
-
Pierre Augier authored
-
Pierre Augier authored
-