mercurial-devel merge requestshttps://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests2020-12-01T17:57:35Zhttps://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/56rhg: initial support for repository requirements2020-12-01T17:57:35ZSimon Sapinrhg: initial support for repository requirementsThe `cat` and `files` sub-commands exit with code 252 if the repository has unknown requirements.The `cat` and `files` sub-commands exit with code 252 if the repository has unknown requirements.https://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/57WIP: play with phabricator auto-refresh2020-12-02T07:43:17ZPierre-Yves DavidWIP: play with phabricator auto-refreshWe are about to add more stageWe are about to add more stagePierre-Yves DavidPierre-Yves Davidhttps://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/31[WIP] implement share safe plan2020-12-08T07:05:50ZPulkit Goyal[WIP] implement share safe planhttps://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/65Topic/default/share safe fixes2021-01-19T02:22:03ZPulkit GoyalTopic/default/share safe fixeshttps://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/62Topic/default/share safe better2021-01-21T13:20:30ZPulkit GoyalTopic/default/share safe betterhttps://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/61Add Python 3.10 support2021-01-25T10:13:43ZVictor StinnerAdd Python 3.10 support* Replace "Py_TYPE(obj) = type;" with "Py_SET_TYPE(obj, type);"
* Add pythoncapi_compat.h header file to get Py_SET_TYPE() on Python
2.7-3.8. Header file added to mercurial/ and
contrib/python-zstandard/zstd/common/.
In Python 3.10,...* Replace "Py_TYPE(obj) = type;" with "Py_SET_TYPE(obj, type);"
* Add pythoncapi_compat.h header file to get Py_SET_TYPE() on Python
2.7-3.8. Header file added to mercurial/ and
contrib/python-zstandard/zstd/common/.
In Python 3.10, Py_TYPE(obj) must not longer be used as an l-value.
pythoncapi_compat.h comes from:
https://github.com/pythoncapi/pythoncapi_compathttps://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/67tests: drop pip test on the client2021-02-02T21:08:43ZJörg Sonnenbergertests: drop pip test on the clientThe PIP testing is fragile, various hacks are included already. It has
been failing persistently in the CI and locally on OpenSuSE. Since
general PIP use requires network access, it is better done during CI
anyway.
Differential Revision...The PIP testing is fragile, various hacks are included already. It has
been failing persistently in the CI and locally on OpenSuSE. Since
general PIP use requires network access, it is better done during CI
anyway.
Differential Revision: https://phab.mercurial-scm.org/D9928https://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/60Topic/default/upgrade refactor2021-02-03T09:24:24ZPulkit GoyalTopic/default/upgrade refactorhttps://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/66contrib: update ci image tag to test black updates2021-02-15T10:07:59ZPulkit Goyalcontrib: update ci image tag to test black updateshttps://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/68ci: test real dependency installation for pip [WIP]2021-02-17T12:59:23ZJörg Sonnenbergerci: test real dependency installation for pip [WIP]In the past, the pip smoke test inhibited actual dependency
installation, but that fails in different environments for setuptools
itself. Since it isn't what we actually want to test (which is pip
install), allow this to call home.
WIP ...In the past, the pip smoke test inhibited actual dependency
installation, but that fails in different environments for setuptools
itself. Since it isn't what we actually want to test (which is pip
install), allow this to call home.
WIP as this part of the test should only be run during CI.https://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/69Topic/default/upgrade refactor2021-03-01T18:35:41ZPulkit GoyalTopic/default/upgrade refactorhttps://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/73Topic/default/tags better2021-03-08T20:32:23ZPulkit GoyalTopic/default/tags betterhttps://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/76commit: reorder if-else conditional to give mergestate info priority2021-03-22T18:42:24ZPulkit Goyalcommit: reorder if-else conditional to give mergestate info priorityLooking at the code now, I was unable to find a good reason as why we only rely
on mergestate extras info after checking whether a filelog parent is ancestor of
other or not.
I mean if we have stored in mergestate that `other` was chose...Looking at the code now, I was unable to find a good reason as why we only rely
on mergestate extras info after checking whether a filelog parent is ancestor of
other or not.
I mean if we have stored in mergestate that `other` was chosed, we should
blindly pick that one.
This cleanup will also help introduce more cases when both `fparent1` and
`fparent2` are non-null but using info from mergestate, we can fastpath.https://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/79rhg: add support for detailed exit code for ConfigParseError2021-03-25T21:42:30ZPulkit Goyalrhg: add support for detailed exit code for ConfigParseErrorThis patch adds basic support for detailed exit code to rhg with support for
ConfigParseError.
rhg right not does not seem to have all and same errors as core hg now which
makes sense since it only implements part of things.This patch adds basic support for detailed exit code to rhg with support for
ConfigParseError.
rhg right not does not seem to have all and same errors as core hg now which
makes sense since it only implements part of things.https://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/81Draft: sidedata: register copies sidedata computer regardless of the revlog v...2021-04-29T22:21:36ZPierre-Yves DavidDraft: sidedata: register copies sidedata computer regardless of the revlog versionRepositories should not gate their sidedata computers based on any requirement,
only their wanted sidedata. A repository might need to generate sidedata wanted
by the peer that it itself does not want.
Differential Revision: https://pha...Repositories should not gate their sidedata computers based on any requirement,
only their wanted sidedata. A repository might need to generate sidedata wanted
by the peer that it itself does not want.
Differential Revision: https://phab.mercurial-scm.org/D10340https://foss.heptapod.net/mercurial/mercurial-devel/-/merge_requests/80rhg: try read [paths] for `--repository` value2021-06-09T09:38:03ZPulkit Goyalrhg: try read [paths] for `--repository` valuehg parses -R and --repository CLI arguments "early" in order to know which
local repository to load config from. (Config can then affect whether or how to
fall back.)
The value of of those arguments can be not only a filesystem path, bu...hg parses -R and --repository CLI arguments "early" in order to know which
local repository to load config from. (Config can then affect whether or how to
fall back.)
The value of of those arguments can be not only a filesystem path, but also an
alias configured in the [paths] section. This part was missing in rhg and this
patch implements that.
The `#if no-rhg` is still not removed completely as those two `[paths]` are read
from `.hg/hgrc` of directory in which the command is running. That will be
implemented in the next patch.