- May 18, 2022
-
-
Raphaël Gomès authored
This helps when diagnosing corruption, and is in general good practice. The information is here, valuable and can be used easily.
-
Raphaël Gomès authored
This is useful when debugging.
-
- Jun 12, 2022
-
-
Ian Moody authored
This has been deprecated since py3.2, and removed entirely in py3.9
-
Ian Moody authored
- don't check for a binary symbol in globals(), which meant it always thought the module wasn't available - don't pass bytes to stdlib methods - return bytes in getchanges where Mercurial expects to see them
-
- Jun 15, 2022
-
-
Ian Moody authored
All the `import elementtree` attempts seem to pre-date py2.5, when it was brought into the standard library, and the manual `cElementTree` fast implementation import has been unnecessary and deprecated since py3.3.
-
- Jun 16, 2022
-
-
Raphaël Gomès authored
-
Raphaël Gomès authored
-
Raphaël Gomès authored
-
Raphaël Gomès authored
-
Raphaël Gomès authored
-
Raphaël Gomès authored
-
- Jun 10, 2022
-
-
Pierre-Yves David authored
With rust supporting more matcher types, we can now take this route in the sparse case too.
-
Pierre-Yves David authored
core is already aware of sparse, so lets move the handful of line of code that deal with this for the sake of simplicity and explicitness.
-
Pierre-Yves David authored
This new output clarify the important part out this merging : we want to be able to record the copy source even it is outside of the sparse profile.
-
Pierre-Yves David authored
The code of the wrapper only act in the case where the file is not tracked, so this has not effect for `untracked`. In addition the message explicitly mention `add` of a file and no test are breaking if we drop this. So we drop this for simplicity and cleanup
-
Pierre-Yves David authored
Core is already aware of sparse, so lets move the handful of line of code that deal with it in `dirstate.rebuild` for the sake of simplicity.
-
Pierre-Yves David authored
core is already aware of sparse, so lets move the handful of line of code that deal with it in `dirstate.walk` for the sake of simplicity.
-
Pierre-Yves David authored
This create a clear signal for when the feature is unused. We could also create an `alwaysmatcher`, but using None is more explicit, so I went for it.
-
- Jun 08, 2022
-
-
Pierre-Yves David authored
Code is now checking if the repository using the sparse feature and that's it. Some code in `debugsparse` still rely on "global" state, as it apply sparse logic before updating the requirement. Cleaning that up is more work that we signed up for, but we could narrow the hack to that specific command.
-
- Jun 10, 2022
-
-
Pierre-Yves David authored
We need to get this test covered by the CI, in the meantime, here is a quick fix.
-
- Jun 14, 2022
-
-
Pierre-Yves David authored
if --files is passed, there was no directory to checks and `msg` was undefined. This is now fixed and tested.
-
- Jun 08, 2022
-
-
Raphaël Gomès authored
This is in case this ever comes up, it's very easy to support, so might as well do it.
-
Raphaël Gomès authored
`IntersectionMatcher` is now implemented in Rust.
-
Raphaël Gomès authored
This will be used in the upcoming support for sparse checkouts in Rust-augmented status and later in rhg support for sparse checkouts.
-
Raphaël Gomès authored
`UnionMatcher` is now implemented in Rust.
-
Raphaël Gomès authored
This will be used in the upcoming support for sparse checkouts in Rust-augmented status and later in rhg support for sparse checkouts.
-
Raphaël Gomès authored
This reduces duplication and will allow for recursive transformation in UnionMatcher.
-
Raphaël Gomès authored
This simplifies the code a lot, allows for some refactoring to come. The original code tried to prevent allocations that were already happening anyway beforehand.
-
- Jun 09, 2022
-
-
Raphaël Gomès authored
At this point in the process, nothing user-visible has happened, it is still safe to fallback. This can happen now that we're going to be using "container matchers" like unionmatcher and intersectionmatcher. This is easier and less error-prone than recursive checking beforehand since only the presence of a transformation case will allow the process to continue.
-
- Jun 14, 2022
-
-
Pierre-Yves David authored
For well tested case, the message can get in the way, so we add a way to disable it.
-
Pierre-Yves David authored
For well tested case, the message can get in the way, so we add a way to disable it.
-
Pierre-Yves David authored
For well tested case, the message can get in the way, so we add a way to disable it.
-
Pierre-Yves David authored
This was the result of a copy paste.
-
Pierre-Yves David authored
For well tested case, the message can get in the way, so we add a way to disable it.
-
Pierre-Yves David authored
We will add options to suppress the message in the coming changeset. The changes will be clearer if the full test is already in place.
-
- May 18, 2022
-
-
Pierre-Yves David authored
This does not really matters as the logic to decide wether or not adding the part is correct and elsewhere. However this seems like a good idea to align this logic witht he semantic of the option.
-
- May 25, 2022
-
-
Pierre-Yves David authored
This make `hg debugbundle --spec` more informative about extra part in the bundle.
-
- May 18, 2022
-
-
Pierre-Yves David authored
If the value is non-default, we display it.
-
Pierre-Yves David authored
This makes it possible to create bundle using changelog-v3. The `hg debugbundle --spec` output is borked, but this will be fixed in coming changesets.
-