mercurial-devel merge requestshttps://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests2023-05-24T21:02:05Zhttps://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/504Draft: streamclone: v32023-05-24T21:02:05ZArseniy AlekseyevDraft: streamclone: v3/notassign_reviewer @mercurial.review
Work on streamclone v3.
Solves the following problems:
- reduces the duration of server-side locking (removes the repo scan from the critical section)
- fixes the bug where concurrent pushes make th.../notassign_reviewer @mercurial.review
Work on streamclone v3.
Solves the following problems:
- reduces the duration of server-side locking (removes the repo scan from the critical section)
- fixes the bug where concurrent pushes make the clone fail (if they split an inline index)
- fixes the bug where corrupted fncache causes clone to succeed and produce corrupted reposArseniy AlekseyevArseniy Alekseyevhttps://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/546Draft: stabletailsort: add (specific) leap computation2023-05-02T18:09:28ZPacien TRAN-GIRARDDraft: stabletailsort: add (specific) leap computation<!--
Welcome to the Mercurial Merge Request creation process:
* Set a simple title for your MR,
* All important information should be contained in your changesets' content or description,
* You can add some workflow-relevant informatio...<!--
Welcome to the Mercurial Merge Request creation process:
* Set a simple title for your MR,
* All important information should be contained in your changesets' content or description,
* You can add some workflow-relevant information here (eg: when this depends on another MR),
* If your changes are not ready for review yet, click `Start the title with Draft:` under the title.
More details here:
* https://www.mercurial-scm.org/wiki/ContributingChanges
* https://www.mercurial-scm.org/wiki/Heptapod
-->https://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/359Draft: debugtemplate: allow using working directory context and template file2023-04-26T04:32:26ZLudovic ChabantDraft: debugtemplate: allow using working directory context and template fileThis makes it possible to run `hg debugtemplate -w` and get a commit template for the pending changes in the working directory, similar to how `hg debugtemplate -r` does it for an already commited changeset.This makes it possible to run `hg debugtemplate -w` and get a commit template for the pending changes in the working directory, similar to how `hg debugtemplate -r` does it for an already commited changeset.Ludovic ChabantLudovic Chabanthttps://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/541Draft: sslutil: set context security level for legacy tls testing (issue6760)2023-04-13T09:33:01ZPacien TRAN-GIRARDDraft: sslutil: set context security level for legacy tls testing (issue6760)<!--
Welcome to the Mercurial Merge Request creation process:
* Set a simple title for your MR,
* All important information should be contained in your changesets' content or description,
* You can add some workflow-relevant informatio...<!--
Welcome to the Mercurial Merge Request creation process:
* Set a simple title for your MR,
* All important information should be contained in your changesets' content or description,
* You can add some workflow-relevant information here (eg: when this depends on another MR),
* If your changes are not ready for review yet, click `Start the title with Draft:` under the title.
More details here:
* https://www.mercurial-scm.org/wiki/ContributingChanges
* https://www.mercurial-scm.org/wiki/Heptapod
-->Mercurial ReviewMercurial Reviewhttps://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/529test-tx-rollback: more lenient glob for kill status (issue6807)2023-04-06T16:50:33ZPacien TRAN-GIRARDtest-tx-rollback: more lenient glob for kill status (issue6807)https://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/528Draft: rhg: expand "~/" in file name from `ui.ignore` config entry2023-04-06T08:54:24ZAndrey ManzharovDraft: rhg: expand "~/" in file name from `ui.ignore` config entry<!--
Welcome to the Mercurial Merge Request creation process:
* Set a simple title for your MR,
* All important information should be contained in your changesets' content or description,
* You can add some workflow-relevant informatio...<!--
Welcome to the Mercurial Merge Request creation process:
* Set a simple title for your MR,
* All important information should be contained in your changesets' content or description,
* You can add some workflow-relevant information here (eg: when this depends on another MR),
* If your changes are not ready for review yet, click `Start the title with Draft:` under the title.
More details here:
* https://www.mercurial-scm.org/wiki/ContributingChanges
* https://www.mercurial-scm.org/wiki/Heptapod
-->https://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/212Draft: commands: add whereami command2023-03-29T19:41:42ZArun KulshreshthaDraft: commands: add whereami commandThis commit adds a new `hg whereami` command that prints the hashes of the
working directory parents. This is similar to the `hg identify` command (or
`hg log -r . -T '{node}'`), except unlike `hg identify`, this command does not
compute...This commit adds a new `hg whereami` command that prints the hashes of the
working directory parents. This is similar to the `hg identify` command (or
`hg log -r . -T '{node}'`), except unlike `hg identify`, this command does not
compute the status or any other information. The goal of this command is to
provide the hash of the current commit with minimal latency, which in turns
allows this information to be used in latency-sensitive contexts (e.g., when
rendering the user's shell prompt). This is similar to using the equivalent git
command (`git rev-parse HEAD`), which has extremely low latency.
The command name and behavior were inspired by the [equivalent command](https://github.com/facebookexperimental/eden/blob/main/eden/scm/lib/hgcommands/src/commands/whereami.rs) from Facebook's
EdenSCM CLI.https://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/513tests: accept a test output change in [tests/test-serve.t]2023-03-22T19:35:45ZArseniy Alekseyevtests: accept a test output change in [tests/test-serve.t]<!--
Welcome to the Mercurial Merge Request creation process:
* Set a simple title for your MR,
* All important information should be contained in your changesets' content or description,
* You can add some workflow-relevant informatio...<!--
Welcome to the Mercurial Merge Request creation process:
* Set a simple title for your MR,
* All important information should be contained in your changesets' content or description,
* You can add some workflow-relevant information here (eg: when this depends on another MR),
* If your changes are not ready for review yet, click `Start the title with Draft:` under the title.
More details here:
* https://www.mercurial-scm.org/wiki/ContributingChanges
* https://www.mercurial-scm.org/wiki/Heptapod
-->https://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/502tests: fix timeout adjustement in delaypush.py2023-03-20T09:43:40ZPierre-Yves Davidtests: fix timeout adjustement in delaypush.py<!--
Welcome to the Mercurial Merge Request creation process:
* Set a simple title for your MR,
* All important information should be contained in your changesets' content or description,
* You can add some workflow-relevant informatio...<!--
Welcome to the Mercurial Merge Request creation process:
* Set a simple title for your MR,
* All important information should be contained in your changesets' content or description,
* You can add some workflow-relevant information here (eg: when this depends on another MR),
* If your changes are not ready for review yet, click `Start the title with Draft:` under the title.
More details here:
* https://www.mercurial-scm.org/wiki/ContributingChanges
* https://www.mercurial-scm.org/wiki/Heptapod
-->https://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/497Draft: dirstate-v2: fix an incorrect handling of readdir errors2023-03-13T12:05:42ZArseniy AlekseyevDraft: dirstate-v2: fix an incorrect handling of readdir errors<!--
Welcome to the Mercurial Merge Request creation process:
* Set a simple title for your MR,
* All important information should be contained in your changesets' content or description,
* You can add some workflow-relevant informatio...<!--
Welcome to the Mercurial Merge Request creation process:
* Set a simple title for your MR,
* All important information should be contained in your changesets' content or description,
* You can add some workflow-relevant information here (eg: when this depends on another MR),
* If your changes are not ready for review yet, click `Start the title with Draft:` under the title.
More details here:
* https://www.mercurial-scm.org/wiki/ContributingChanges
* https://www.mercurial-scm.org/wiki/Heptapod
-->https://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/486fastexport: simple improvements2023-03-10T03:52:23ZFelipe Contrerasfastexport: simple improvementsThe main purpose of this series is to fix an inconsistency between git and hg commit messages. All conversion tools add a newline to hg commit messages, see for example ([hg-git](https://foss.heptapod.net/mercurial/hg-git/-/commit/0e0a2d...The main purpose of this series is to fix an inconsistency between git and hg commit messages. All conversion tools add a newline to hg commit messages, see for example ([hg-git](https://foss.heptapod.net/mercurial/hg-git/-/commit/0e0a2d20deed9552df41153fde587a8145b1c64d), [git-remote-hg](https://github.com/felipec/git-remote-hg/commit/197e2b114725bfc997950c4335abec9395a1a5c9), and [hg-fast-export](https://github.com/frej/fast-export/commit/4c10270302979f76d3bf143a2c3b3374c1b36e2c).
`hg fastexport` should do the same.
While at it, I reorganized the code of `write_data()` a little bit.https://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/329Draft: Rust fixes around dirstate-v22023-03-06T10:45:22ZRaphaël GomèsDraft: Rust fixes around dirstate-v2<!--
Welcome to the Mercurial Merge Request creation process:
* Set a simple title for your MR,
* All important information should be contained in your changesets' content or description,
* You can add some workflow-relevant informatio...<!--
Welcome to the Mercurial Merge Request creation process:
* Set a simple title for your MR,
* All important information should be contained in your changesets' content or description,
* You can add some workflow-relevant information here (eg: when this depends on another MR),
* If your changes are not ready for review yet, click `Start the title with Draft:` under the title.
More details here:
* https://www.mercurial-scm.org/wiki/ContributingChanges
* https://www.mercurial-scm.org/wiki/Heptapod
-->https://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/310tests: run most tests with dirstate v22023-02-24T16:06:14ZArseniy Alekseyevtests: run most tests with dirstate v2The commit "dirstate-v2: do not put the dirstate data file in a transaction" is duplicated with MR#309.
If the new CI variant is not desired, I'm happy to remove it, but I still want to keep the test tweaks.The commit "dirstate-v2: do not put the dirstate data file in a transaction" is duplicated with MR#309.
If the new CI variant is not desired, I'm happy to remove it, but I still want to keep the test tweaks.Arseniy AlekseyevArseniy Alekseyevhttps://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/454dirstate-scoping [15]: scoping cleanup2023-02-22T13:34:59ZPierre-Yves Daviddirstate-scoping [15]: scoping cleanupa handful of cleanup gathered before jumping on a back of a larger dragon.
<!--
Welcome to the Mercurial Merge Request creation process:
* Set a simple title for your MR,
* All important information should be contained in your changes...a handful of cleanup gathered before jumping on a back of a larger dragon.
<!--
Welcome to the Mercurial Merge Request creation process:
* Set a simple title for your MR,
* All important information should be contained in your changesets' content or description,
* You can add some workflow-relevant information here (eg: when this depends on another MR),
* If your changes are not ready for review yet, click `Start the title with Draft:` under the title.
More details here:
* https://www.mercurial-scm.org/wiki/ContributingChanges
* https://www.mercurial-scm.org/wiki/Heptapod
-->Pierre-Yves DavidPierre-Yves Davidhttps://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/451distate-scoping [14] : enforce scoping on more method2023-02-22T13:34:59ZPierre-Yves Daviddistate-scoping [14] : enforce scoping on more method<!--
Welcome to the Mercurial Merge Request creation process:
* Set a simple title for your MR,
* All important information should be contained in your changesets' content or description,
* You can add some workflow-relevant informatio...<!--
Welcome to the Mercurial Merge Request creation process:
* Set a simple title for your MR,
* All important information should be contained in your changesets' content or description,
* You can add some workflow-relevant information here (eg: when this depends on another MR),
* If your changes are not ready for review yet, click `Start the title with Draft:` under the title.
More details here:
* https://www.mercurial-scm.org/wiki/ContributingChanges
* https://www.mercurial-scm.org/wiki/Heptapod
-->Pierre-Yves DavidPierre-Yves Davidhttps://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/418Draft: retire safehasattr2023-02-03T10:40:04ZPierre-Yves DavidDraft: retire safehasattrPierre-Yves DavidPierre-Yves Davidhttps://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/361resourceutil: suppress DeprecationWarning (issue6731)2023-01-24T10:35:22ZJason R. Coombsresourceutil: suppress DeprecationWarning (issue6731)https://bz.mercurial-scm.org/show_bug.cgi?id=6731
<!--
Welcome to the Mercurial Merge Request creation process:
* Set a simple title for your MR,
* All important information should be contained in your changesets' content or descripti...https://bz.mercurial-scm.org/show_bug.cgi?id=6731
<!--
Welcome to the Mercurial Merge Request creation process:
* Set a simple title for your MR,
* All important information should be contained in your changesets' content or description,
* You can add some workflow-relevant information here (eg: when this depends on another MR),
* If your changes are not ready for review yet, click `Start the title with Draft:` under the title.
More details here:
* https://www.mercurial-scm.org/wiki/ContributingChanges
* https://www.mercurial-scm.org/wiki/Heptapod
-->https://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/377faster checks around a large [hg update]2023-01-12T13:17:22ZArseniy Alekseyevfaster checks around a large [hg update]
<!--
Welcome to the Mercurial Merge Request creation process:
* Set a simple title for your MR,
* All important information should be contained in your changesets' content or description,
* You can add some workflow-relevant informati...
<!--
Welcome to the Mercurial Merge Request creation process:
* Set a simple title for your MR,
* All important information should be contained in your changesets' content or description,
* You can add some workflow-relevant information here (eg: when this depends on another MR),
* If your changes are not ready for review yet, click `Start the title with Draft:` under the title.
More details here:
* https://www.mercurial-scm.org/wiki/ContributingChanges
* https://www.mercurial-scm.org/wiki/Heptapod
-->https://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/262Draft: shelve: handle empty parents and nodestoremove in shelvedstate (issue6...2022-11-05T23:49:47ZJason R. CoombsDraft: shelve: handle empty parents and nodestoremove in shelvedstate (issue6748)<!--
Welcome to the Mercurial Merge Request creation process:
* Set a simple title for your MR,
* All important information should be contained in your changesets' content or description,
* You can add some workflow-relevant informatio...<!--
Welcome to the Mercurial Merge Request creation process:
* Set a simple title for your MR,
* All important information should be contained in your changesets' content or description,
* You can add some workflow-relevant information here (eg: when this depends on another MR),
* If your changes are not ready for review yet, click `Start the title with Draft:` under the title.
More details here:
* https://www.mercurial-scm.org/wiki/ContributingChanges
* https://www.mercurial-scm.org/wiki/Heptapod
-->Jason R. CoombsJason R. Coombshttps://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/254Draft: perf-unbundle: do a quick and dirty fix to make it run on more comit2022-11-04T03:52:08ZPierre-Yves DavidDraft: perf-unbundle: do a quick and dirty fix to make it run on more comitWithout this change, the perf commands fails within the
f67741e8264b::18415fc918a1 range (boundary excluded).
Check inline comment for details.Without this change, the perf commands fails within the
f67741e8264b::18415fc918a1 range (boundary excluded).
Check inline comment for details.Pierre-Yves DavidPierre-Yves David