Did you figure hit sout? I just did a test locally and the backout
worked as expected. In the latest head I ran hg backout -r 2
--no-commit (I wanted to verify it). When I ran that, I was presented
with a merge screen to handle the conflict caused by the backout, and
afterwards I had the
>>> "MK" == Marcin Kasperski writes:
>> ok. I wanted to play with various versions and for the moment not rely
>> on pip. The reason is that the artemis extension is a bit orphaned (but
>> important to me). It actually only works till hg 5.2
> For the sake of clarity: I don't know
New changeset (1 on stable) in mercurial:
https://www.mercurial-scm.org/repo/hg/rev/49f8ba4febec
changeset: 45352:49f8ba4febec
branch: stable
tag: tip
parent: 45273:3d414dce2d40
user:Cédric Krier
date:Sun Aug 02 17:40:35 2020 +0200
summary: keepalive: Do
> ok. I wanted to play with various versions and for the moment not rely
> on pip. The reason is that the artemis extension is a bit orphaned (but
> important to me). It actually only works till hg 5.2
For the sake of clarity: I don't know or use artemis extension (in fact,
I don't know what it
> Could you use some versions scheme to explicitly abort when the helper
> version are out of sync with the extensions ?
All setup's have proper dependencies, including versions, like here:
https://foss.heptapod.net/mercurial/mercurial-all_dirs/-/blob/branch/default/setup.py#L20
therefore
pulkit created this revision.
Herald added a reviewer: hg-reviewers.
Herald added a subscriber: mercurial-patches.
REVISION SUMMARY
We add them to `WORKING_DIR_REQUIREMENTS` too as they should be stored in
`.hg/requires` and have information about the type of working copy.
REPOSITORY
rHG
https://bz.mercurial-scm.org/show_bug.cgi?id=6395
Bug ID: 6395
Summary: test-check-format.t is missing testrepo requirement
Product: Mercurial
Version: unspecified
Hardware: PC
OS: Linux
Status: UNCONFIRMED
