mercurial-devel merge requestshttps://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests2023-12-12T11:26:38Zhttps://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/731persistent-nodemap: avoid writing nodemap for empty revlog2023-12-12T11:26:38ZPierre-Yves Davidpersistent-nodemap: avoid writing nodemap for empty revlogThere is currently nothing known to write such empty nodemap right now, but the change we are preparing on default reveal this issue. So I rather fix it on stable.
<!--
Welcome to the Mercurial Merge Request creation process:
* Set a ...There is currently nothing known to write such empty nodemap right now, but the change we are preparing on default reveal this issue. So I rather fix it on stable.
<!--
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/51merge-newnode work2020-10-15T12:52:46ZPulkit Goyalmerge-newnode workWe should for whether bids contain a combination of actions which conflict with
each other. Since right now we only have couple of such combination, and
combinations also consist of two actions, we were checking for them only when
length...We should for whether bids contain a combination of actions which conflict with
each other. Since right now we only have couple of such combination, and
combinations also consist of two actions, we were checking for them only when
length of bids is 2. Let's check that irrespective of the length of bids.https://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/49merge-newnode final2020-09-28T12:16:13ZPulkit Goyalmerge-newnode finalhttps://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/90largefile: synchronise the dirstate within a `parentchange` context2021-07-16T13:20:18ZPierre-Yves Davidlargefile: synchronise the dirstate within a `parentchange` contextSemantically these changes are made to adjust the dirstate after a commit, so it
should be in a `parentchange` context.Semantically these changes are made to adjust the dirstate after a commit, so it
should be in a `parentchange` context.https://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/64largefiles: remove unused imports2021-01-14T10:33:36ZPulkit Goyallargefiles: remove unused importsThis fixes test-check-pyflakes.tThis fixes test-check-pyflakes.thttps://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/16improv test amend2020-02-07T22:48:54ZPierre-Yves Davidimprov test amendhttps://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/630heptapod-ci: remove push exception for named branches2023-07-04T10:35:44ZRaphaël Gomèsheptapod-ci: remove push exception for named branches<!--
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/28get test to pass with chg2020-07-22T11:22:13ZPierre-Yves Davidget test to pass with chgI am not aware of any regular run of the test with chg. As a result they borken again. Lets fix the test and add this case to the CI runs.I am not aware of any regular run of the test with chg. As a result they borken again. Lets fix the test and add this case to the CI runs.https://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/11fix remote filelog race2020-02-08T00:02:14ZPierre-Yves Davidfix remote filelog raceCreating a MR to be able to reference it.Creating a MR to be able to reference it.https://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/7Fix last uncheck background process2020-02-08T00:02:32ZBoris FeldFix last uncheck background processhttps://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/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/82exit code2021-06-11T07:30:09ZPulkit Goyalexit codeThis will help us in better handling of error caused when trying to
load `--config` values.
Differential Revision: https://phab.mercurial-scm.org/D10837This will help us in better handling of error caused when trying to
load `--config` values.
Differential Revision: https://phab.mercurial-scm.org/D10837https://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/75exchange: stop advertising rev-branch-cache bundle capability2021-03-05T04:12:19ZJörg Sonnenbergerexchange: stop advertising rev-branch-cache bundle capabilitySince Mercurial 5.7, the corresponding bundle part is ignored as
redundant. Stop advertising it so that peers don't have to spend time
creating or transfering it.
Differential Revision: https://phab.mercurial-scm.org/D10114Since Mercurial 5.7, the corresponding bundle part is ignored as
redundant. Stop advertising it so that peers don't have to spend time
creating or transfering it.
Differential Revision: https://phab.mercurial-scm.org/D10114https://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/71error: remove shortening of node in error message2021-03-08T20:32:22ZPulkit Goyalerror: remove shortening of node in error messageThis makes it difficult to figure what exactly was node on which LookupError was
called if we only have the error message.
I was debugging an error message which contained a short node and I tried to
find out which callers raise LookupE...This makes it difficult to figure what exactly was node on which LookupError was
called if we only have the error message.
I was debugging an error message which contained a short node and I tried to
find out which callers raise LookupError with a short node. This turned out to
be wrong because we short-ed the node before printing.
If a short node is to be displayed, that should be done by callers.https://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/70error: remove shortening of node in error message2021-02-15T10:59:41ZPulkit Goyalerror: remove shortening of node in error messageThis makes it difficult to figure what exactly was node on which LookupError was
called if we only have the error message.
I was debugging an error message which contained a short node and I tried to
find out which callers raise LookupE...This makes it difficult to figure what exactly was node on which LookupError was
called if we only have the error message.
I was debugging an error message which contained a short node and I tried to
find out which callers raise LookupError with a short node. This turned out to
be wrong because we short-ed the node before printing.
Let's be explicit and show whatever is passed to LookupError. If a short node is
to be displayed, that should be done by callers.https://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/132Enforce narrowacl in narrow_widen2022-05-26T23:14:09ZidlsoftEnforce narrowacl in narrow_widenDifferential Revision: https://phab.mercurial-scm.org/D12600Differential Revision: https://phab.mercurial-scm.org/D12600https://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/131Enforce narrowacl in narrow_widen2022-05-26T22:33:34ZidlsoftEnforce narrowacl in narrow_widenDifferential Revision: https://phab.mercurial-scm.org/D12600Differential Revision: https://phab.mercurial-scm.org/D12600https://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/129Enforce narrowacl in narrow_widen2022-05-26T16:44:30ZidlsoftEnforce narrowacl in narrow_widenDifferential Revision: https://phab.mercurial-scm.org/D12600Differential Revision: https://phab.mercurial-scm.org/D12600https://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/127Draft: worker: fix handling of EINTR2022-05-28T19:42:36ZManuel JacobDraft: worker: fix handling of EINTR