Evolve 11.1.3 released

. This way some users can start using topic namespaces, and others can avoid any interactions with this new feature until it's more complete and less experimental. Thanks to all the people involved: * Anton Shestakov * Pierre-Yves David ## Evolve: 11.1.3 * no changes, just a version bump

Evolve 11.1.3 released

. This way some users can start using topic namespaces, and others can avoid any interactions with this new feature until it's more complete and less experimental. Thanks to all the people involved: * Anton Shestakov * Pierre-Yves David ## Evolve: 11.1.3 * no changes, just a version bump

Evolve 11.1.2 released

was fixed that made hg backout to fail in commitstatus function (which runs after the job is already done) in Mercurial versions 5.7 through 6.5 with topic extension enabled. Thanks to all the people involved: * Anton Shestakov * Zeger Van de Vannet ## Evolve: 11.1.2 * compatibility

Evolve 11.1.2 released

was fixed that made hg backout to fail in commitstatus function (which runs after the job is already done) in Mercurial versions 5.7 through 6.5 with topic extension enabled. Thanks to all the people involved: * Anton Shestakov * Zeger Van de Vannet ## Evolve: 11.1.2 * compatibility

Evolve 11.1.1 released

ough no code changes were required. Thanks to all the people involved: * Anton Shestakov * Manuel Jacob * Pierre-Yves David ## Evolve: 11.1.1 * compatibility with Mercurial 6.6 * evolve: fix typo in "mercurial" and let hasmemmergestate be True sometimes * uncom

Evolve 11.1.1 released

ough no code changes were required. Thanks to all the people involved: * Anton Shestakov * Manuel Jacob * Pierre-Yves David ## Evolve: 11.1.1 * compatibility with Mercurial 6.6 * evolve: fix typo in "mercurial" and let hasmemmergestate be True sometimes * uncom

Re: mercurial-scm.org down

пн, 22 янв. 2024 г. в 08:18, David Soria Parra : > > http://mercurial-scm.org is still broken. That is the HTTP. I assume the > redirect to HTTPs is broken Right, I think I fixed it. Thanks for reporting! ___ Mercurial mailing list

Re: Cloning to a downgraded repository - examples don't seem to work

06.01.2024 07:16, Chris Green пишет: On Fri, Jan 05, 2024 at 05:06:05PM -0300, Anton Shestakov wrote: 03.01.2024 08:50, Chris Green пишет: I want to clone this repository so that I can use it with some older versions of mercurial that don't have share-safe, so I did:- hg --config

Re: Cloning to a downgraded repository - examples don't seem to work

03.01.2024 08:50, Chris Green пишет: I want to clone this repository so that I can use it with some older versions of mercurial that don't have share-safe, so I did:- hg --config format.share-safe=0 clone --pull .cfg .newcfg The config option you're looking for is

Evolve 11.1.0 released

) was dropped. Thanks to all the people involved: * Anton Shestakov * Jason R. Coombs * Mathias De Mare * Matt Harbison * Pierre-Yves David ## Evolve: 11.1.0 * remove deprecated evolve.serveronly extension, evolve extension is recommended for all users, clients and servers * evolve

Re: partial publish on push

11.08.2023 11:37, Josef 'Jeff' Sipek пишет: On Fri, Aug 11, 2023 at 17:32:40 +0300, Mitchell Elutovich wrote: As discussed, to turn off the auto publishing of changesets that are pushed, the target repo needs to be defined with phases.publish=false. We only partially want that behavior. I

Re: moving non publishing changesets between secret and draft phases and back to secret

10.08.2023 16:05, Mitchell Elutovich пишет: Just to highlight for this scenario, even though we've already discussed, when the draft changeset is "pushed", the *target *repo that is being pushed into will need to have off the auto publishing of draft changesets. [phases] publish = false

Re: moving non publishing changesets between secret and draft phases and back to secret

10.08.2023 10:29, Friedrich Hagedorn пишет: Am Wed, Aug 09, 2023 at 02:31:37PM -0300 schrieb Anton Shestakov: If you're using secret phase to simply prevent accidentally pushing those commits, maybe it'd be better to use a default revset instead. See `hg This should say "to simply pr

Re: moving non publishing changesets between secret and draft phases and back to secret

Secret phase works really well when only one person has access to the secrets (: To clarify, the situation in this thread is that two developers want to occasionally share some commits, but only between themselves and not with the main development repo. Secret phase is not very convenient in

Re: moving non publishing changesets between secret and draft phases and back to secret

09.08.2023 05:39, Mitchell Elutovich пишет: However for my co-worker, I'm not sure he would let the addition of auto-publish=abort (or he would perhaps just always use --publish and defeat the purpose); for his dev repo if I push the changesets (secret -> draft -> push -> secret ), is there

Social presence 2023

Hey all, This is just a quick email to start a brainstorming thread about our public presence on the Internet. We have some presence at the moment, e.g. https://wiki.mercurial-scm.org/SocialMedia https://wiki.mercurial-scm.org/ProjectInfrastructure I'm not sure how active these accounts

Evolve 11.0.2 released

We released a new version of the evolve extension: 11.0.2. As usual, the release is available on PyPI, and upgrade is recommended. This is a bugfix release. The most notable change is compatibility with the upcoming Mercurial 6.5. Thanks to all the people involved: * Anton Shestakov

Re: Unable to Mercurial in $HOME directory

пн, 26 июн. 2023 г. в 14:12, Stephen Rasku : > Typically, I clone the repo into a sub-directory and then move the .hg file > up one directory to the $HOME directory. I've never had problems with this > before on multiple systems. But now I am getting the following error: I'm not exactly sure

Re: Using Evolve 11.0.1 with Mercurial 6.4

25.05.2023 09:41, Faheem Mitha пишет: Hi folks, I'm currently running Mercurial 6.3, and was thinking of upgrading to 6.4. I was just wondering what the correct version of Evolve to upgrade to was. It looks from the changelog that 11.0.1 is the right version. So should I use that? Yes. I

Re: Any way to prevent Evolve's `metaedit` from opening the message?

Yeah, I think metaedit was created as an ad-hoc solution to edit commit messages, and then grew some flags for user and date, and even --fold for some reason. Internally it can prevent editor from opening (e.g. when -m or -l is present), but there's no way to do it from CLI. It's not a very

Evolve 11.0.1 released

We released a new version of the evolve extension: 11.0.1. As usual, the release is available on PyPI, and upgrade is recommended. This is a bugfix release. The most notable change is compatibility with the upcoming Mercurial 6.4. Thanks to all the people involved: * Anton Shestakov

Evolve 11.0.0 released

and serverminitopic extensions were deprecated; evolve and topic extensions are now recommended for both clients and servers. Thanks to all the people involved: * Anton Shestakov * Georges Racinet * Luke Granger-Brown * Matt Harbison * pacien * Pierre-Yves David * Sushil khanchi

Re: Testing an RC of evolve 11.0.0 and topic 1.0.0

14.02.2023 17:20, Georges Racinet пишет: Internally, Heptapod relies on the `branch:topic` syntax, more specifically as keys in the branchmap. Well, it relies on lots of Mercurial and evolve internals (I dare not say APIs). In 11.0.0rc0+ branchmap will have keys in the

Re: Testing an RC of evolve 11.0.0 and topic 1.0.0

30.01.2023 19:24, Anton Shestakov пишет: The release candidate is coming out in the next few days, and the final feature release will most likely be ready in about 2 weeks after that. During these 2 weeks you can reach out to us and tell if you notice something being broken, and we'll

Re: Testing an RC of evolve 11.0.0 and topic 1.0.0

30.01.2023 19:24, Anton Shestakov пишет: The release candidate is coming out in the next few days, and the final feature release will most likely be ready in about 2 weeks after that. During these 2 weeks you can reach out to us and tell if you notice something being broken, and we'll

Evolve 11.0.0rc0 released

; evolve and topic extensions are now recommended for both clients and servers. Thanks to all the people involved: * Anton Shestakov * Luke Granger-Brown * Matt Harbison * pacien * Pierre-Yves David * Sushil khanchi ## Evolve: 11.0.0rc0 * deprecate evolve.serveronly extension, evolve

Re: Testing an RC of evolve 11.0.0 and topic 1.0.0

04.02.2023 22:56, Uwe Brauer пишет: Maybe we have a misunderstanding here. I don't mean the result hg branches I meant that sometimes hg log (with my template, I am not going to post here would give me) ◍ changeset: 674:5c76f339a2eb │ tag: tip │ Branch:

Re: Testing an RC of evolve 11.0.0 and topic 1.0.0

04.02.2023 14:56, Uwe Brauer пишет: 03.02.2023 00:34, Uwe Brauer пишет: By "this" do you mean "branch:topic" or "branch//topic"? I meant "branch//topic" So can I switch the new namespace feature of, if I don't like it? That depends on what you think "the new namespace feature" is. If

Re: Testing an RC of evolve 11.0.0 and topic 1.0.0

03.02.2023 00:34, Uwe Brauer пишет: Hello, users of Mercurial, Evolve and/or Topic! We're planning to release a feature release candidate of evolve and topic extensions that contains an implementation of a concept that was in the plans for quite some time: topic namespaces (the name could

Are you using evolve.serveronly and serverminitopic extensions?

Hello, users of Mercurial, Evolve and/or Topic! Some of you may be using the following server-only extensions: evolve.serveronly and serverminitopic, that live in the same repo as regular evolve extension: https://www.mercurial-scm.org/repo/evolve These extensions were used by Bitbucket when

Are you using evolve.serveronly and serverminitopic extensions?

Hello, users of Mercurial, Evolve and/or Topic! Some of you may be using the following server-only extensions: evolve.serveronly and serverminitopic, that live in the same repo as regular evolve extension: https://www.mercurial-scm.org/repo/evolve These extensions were used by Bitbucket when

Testing an RC of evolve 11.0.0 and topic 1.0.0

Hello, users of Mercurial, Evolve and/or Topic! We're planning to release a feature release candidate of evolve and topic extensions that contains an implementation of a concept that was in the plans for quite some time: topic namespaces (the name could change, if we find something better)

Testing an RC of evolve 11.0.0 and topic 1.0.0

Hello, users of Mercurial, Evolve and/or Topic! We're planning to release a feature release candidate of evolve and topic extensions that contains an implementation of a concept that was in the plans for quite some time: topic namespaces (the name could change, if we find something better)

Evolve 10.5.3 released

with Mercurial 6.3 (no changes to code were required). Thanks to all the people involved: * Anton Shestakov * Matt Harbison * Raphaël Gomès ## Evolve: 10.5.3 * compatibility with Mercurial 6.3 * evolve: make obs-hash-range cache and stable-range cache (that both use SQLite databases) slightly

Evolve 10.5.2 released

fail", but the extensions continue being fully compatible with Python 2.7, and will be compatible as long as there's support for older hg versions (currently the oldest supported version is 4.8). Thanks to all the people involved: * Anton Shestakov ## Evolve: 10.5.2 * compatibility with

Evolve 10.5.3 released

with Mercurial 6.3 (no changes to code were required). Thanks to all the people involved: * Anton Shestakov * Matt Harbison * Raphaël Gomès ## Evolve: 10.5.3 * compatibility with Mercurial 6.3 * evolve: make obs-hash-range cache and stable-range cache (that both use SQLite databases) slightly

Re: Bug in evolve?!

04.11.2022 23:30, Sebastian Unger пишет: Hi Anton, Have you gotten any further with this? I didn't have time to refactor the code, but here's my patch to fix just this issue: https://foss.heptapod.net/mercurial/evolve/-/merge_requests/463 Feel free to leave feedback there or as a reply to

Re: Bug in evolve?!

25.10.2022 03:27, Sebastian Unger пишет: Hi Guys, hg next does not appear to always do what I think it should. If there's more than one child but some need evolving and some don't, then it does not always evolve them. I have attached a script that reproduces the issue for me. *WARNING: The

Evolve 10.5.2 released

fail", but the extensions continue being fully compatible with Python 2.7, and will be compatible as long as there's support for older hg versions (currently the oldest supported version is 4.8). Thanks to all the people involved: * Anton Shestakov ## Evolve: 10.5.2 * compatibility with

D12626: revlog: use %d to format int instead of %lu (issue6565)

av6 created this revision. Herald added a reviewer: hg-reviewers. Herald added a subscriber: mercurial-patches. REVISION SUMMARY The issue says gcc warns that the data types don't match. I couldn't reproduce the warning locally for some reason, but this patch shouldn't break things. Maybe

D12622: doc: use an absolute path in sys.path

av6 created this revision. Herald added a reviewer: hg-reviewers. Herald added a subscriber: mercurial-patches. REVISION SUMMARY The idea and rationale is similar to https://phab.mercurial-scm.org/D12599 (landed as 1b6e381521c5

D12621: check-py3-compat: use an absolute path in sys.path

av6 created this revision. Herald added a reviewer: hg-reviewers. Herald added a subscriber: mercurial-patches. REVISION SUMMARY The idea and rationale is similar to https://phab.mercurial-scm.org/D12599 (landed as 1b6e381521c5

D12620: tests: make sure .js files stay in ASCII encoding (issue6559)

av6 created this revision. Herald added a reviewer: hg-reviewers. Herald added a subscriber: mercurial-patches. REPOSITORY rHG Mercurial BRANCH default REVISION DETAIL https://phab.mercurial-scm.org/D12620 AFFECTED FILES tests/test-check-encoding.t CHANGE DETAILS diff --git

D12598: tests: make sure .js files stay in ASCII encoding (issue6559)

av6 created this revision. Herald added a reviewer: hg-reviewers. Herald added a subscriber: mercurial-patches. REPOSITORY rHG Mercurial BRANCH default REVISION DETAIL https://phab.mercurial-scm.org/D12598 AFFECTED FILES tests/test-check-encoding.t CHANGE DETAILS diff --git

D12597: followlines: don't put Unicode directly into the .js file (issue6559)

av6 created this revision. Herald added a reviewer: hg-reviewers. Herald added a subscriber: mercurial-patches. REVISION SUMMARY Apparently some web server setups may serve this file in a different encoding than UTF-8, and that results in visual garbage in the followlines button that

Re: "hg push" hangs for one minute (exactly one minute)

чт, 28 апр. 2022 г. в 23:12, Ernie Rael : > > On 4/28/22 12:46 PM, Anton Shestakov wrote: > > Looks like either another process is holding a lock on caches or the > > FS doesn't support locking mechanisms that sqlite3 needs. > > > > If you want to dig further into

Re: "hg push" hangs for one minute (exactly one minute)

Looks like either another process is holding a lock on caches or the FS doesn't support locking mechanisms that sqlite3 needs. If you want to dig further into this, check around these files: .hg/cache/evoext_stablerange_v2.sqlite and .hg/cache/evoext_obshashrange_v2.sqlite

Re: "hg push" hangs for one minute (exactly one minute)

There are also --debug and --profile, maybe they can help. Although some parts of the push process may not have debug logging, and profiling is for when you wish to delve into source code. I suspect there's something in the setup of the network or network file system, because 1 minute looks like

D12589: tests: fix misspelling of supersede

av6 created this revision. Herald added a reviewer: hg-reviewers. Herald added a subscriber: mercurial-patches. REPOSITORY rHG Mercurial BRANCH default REVISION DETAIL https://phab.mercurial-scm.org/D12589 AFFECTED FILES tests/test-push-checkheads-partial-C1.t

Evolve 10.5.1 released

/show_bug.cgi?id=6669, this was fixed. There are also changes that should help Debian package maintainers; e.g. it's now possible to use system cbor instead of the one we vendor. Thanks to all the people involved: * Andrej Shadura * Anton Shestakov * Georges Racinet * Pierre-Yves David ## Evolve

Evolve 10.5.1 released

/show_bug.cgi?id=6669, this was fixed. There are also changes that should help Debian package maintainers; e.g. it's now possible to use system cbor instead of the one we vendor. Thanks to all the people involved: * Andrej Shadura * Anton Shestakov * Georges Racinet * Pierre-Yves David ## Evolve

Evolve 10.5.0 released

). With an up-to-date client and server you should expect hg push to take much less time. Also compatibility with Mercurial 4.7 was dropped in this release. Thanks to all the people involved: * Anton Shestakov * Faheem Mitha * Georges Racinet * Kim Alvefur * Raphaël Gomès * Simon Sapin

Evolve 10.5.0 released

). With an up-to-date client and server you should expect hg push to take much less time. Also compatibility with Mercurial 4.7 was dropped in this release. Thanks to all the people involved: * Anton Shestakov * Faheem Mitha * Georges Racinet * Kim Alvefur * Raphaël Gomès * Simon Sapin

D12195: obsolete: don't use os.stat in repo.obsstore.__nonzero__ if it's static HTTP

av6 created this revision. Herald added a reviewer: hg-reviewers. Herald added a subscriber: mercurial-patches. REVISION SUMMARY If a repo is accessed via static HTTP, then we obviously can't use os.stat() to just peek at the file size. Let's download the entire file to check its size.

D12157: scmutil: obsrevs is already a frozenset

av6 created this revision. Herald added a reviewer: hg-reviewers. Herald added a subscriber: mercurial-patches. REPOSITORY rHG Mercurial BRANCH default REVISION DETAIL https://phab.mercurial-scm.org/D12157 AFFECTED FILES mercurial/scmutil.py CHANGE DETAILS diff --git

D12156: obsolete: always return frozensets from obsolete.getrevs()

av6 created this revision. Herald added a reviewer: hg-reviewers. Herald added a subscriber: mercurial-patches. REVISION SUMMARY getrevs function already returns an empty frozenset when there is no obsstore, but let's make sure to return a frozenset in any case. This makes it possible to

D12138: branchmap: split a long condition in branchcache.validfor(), add comments

av6 created this revision. Herald added a reviewer: hg-reviewers. Herald added a subscriber: mercurial-patches. REPOSITORY rHG Mercurial BRANCH default REVISION DETAIL https://phab.mercurial-scm.org/D12138 AFFECTED FILES mercurial/branchmap.py CHANGE DETAILS diff --git

D12135: branchmap: don't add branch entries if there are no heads

av6 created this revision. Herald added a reviewer: hg-reviewers. Herald added a subscriber: mercurial-patches. REVISION SUMMARY We definitely don't want any empty entries to be present in repo.branchmap() just for the sake of not breaking test-notify.t. No test changes required because

D12134: notify: don't produce errors if a revision is not found

av6 created this revision. Herald added a reviewer: hg-reviewers. Herald added a subscriber: mercurial-patches. REVISION SUMMARY Notify extension has a way to only subscribe to a specific revset, such as "branch(foo)". Before this patch, when there was no branch with that name, it would

D12121: obsolete: don't import from .node twice

av6 created this revision. Herald added a reviewer: hg-reviewers. Herald added a subscriber: mercurial-patches. REVISION SUMMARY See d55b71393907 . REPOSITORY rHG Mercurial BRANCH default REVISION DETAIL

D12120: dagop: don't import nullrev from .node twice

av6 created this revision. Herald added a reviewer: hg-reviewers. Herald added a subscriber: mercurial-patches. REVISION SUMMARY See 59fa3890d40a . REPOSITORY rHG Mercurial BRANCH default REVISION DETAIL

D12097: branchmap: skip obsolete revisions while computing heads

av6 created this revision. Herald added a reviewer: hg-reviewers. Herald added a subscriber: mercurial-patches. REVISION SUMMARY It's time to make this part of core Mercurial obsolescence-aware. Not considering obsolete revisions when computing heads is clearly what Mercurial should do.

D12098: discovery: port _postprocessobsolete() changes from evolve, add tests

av6 created this revision. Herald added a reviewer: hg-reviewers. Herald added a subscriber: mercurial-patches. REVISION SUMMARY Let's make this function obsolescence-aware as well. Now we check that revisions are not obsolete first, and only then check that they are going to be common

D12100: obsolete: make sure windows tests pass when stat() is given a URL

av6 created this revision. Herald added a reviewer: hg-reviewers. Herald added a subscriber: mercurial-patches. REVISION SUMMARY This is a band-aid for test-static-http.t breakage on windows. On windows this exception is not ENOENT, but EINVAL (because of `:` symbol, for example).

D12099: destutil: if wdp is obsolete, update to the closest non-obsolete ancestor

av6 created this revision. Herald added a reviewer: hg-reviewers. Herald added a subscriber: mercurial-patches. REVISION SUMMARY As the original comments suggest, using prune as a model here was an existing idea, and now this patch implements it. I think it would be even better to do

D12092: interfaces: add missing caches kwarg of localrepo.updatecaches()

av6 created this revision. Herald added a reviewer: hg-reviewers. Herald added a subscriber: mercurial-patches. REVISION SUMMARY Added to localrepo: in 1337bfaa88ca , added to the interface: now. REPOSITORY rHG

Re: Evolve mini-sprint January 7th

Happy New Year everyone! I hope you celebrated enough to enjoy the holiday season to the fullest, but not enough to forget that there's a sprint this week, Friday, January 7th. Hello everyone, Keeping the tradition of monthly mini-sprints related to all things Mercurial, the next one will be

Re: Evolve mini-sprint January 7th

Happy New Year everyone! I hope you celebrated enough to enjoy the holiday season to the fullest, but not enough to forget that there's a sprint this week, Friday, January 7th. Hello everyone, Keeping the tradition of monthly mini-sprints related to all things Mercurial, the next one will be

Re: Evolve mini-sprint January 7th

Happy New Year everyone! I hope you celebrated enough to enjoy the holiday season to the fullest, but not enough to forget that there's a sprint this week, Friday, January 7th. Hello everyone, Keeping the tradition of monthly mini-sprints related to all things Mercurial, the next one will be

Re: repository with subrespository: I am stuck with a nested nested path problem

> abort: path 'Neu-Einstufung/DocX-Neu' is inside nested repo 'Neu-Einstufung' This suggests that hg tries to handle a file from a subrepo in the context of the main repo. This could happen when that file was a part of the main repo and then it was moved to a subrepo, and hg is trying to e.g.

Re: repository with subrespository: I am stuck with a nested nested path problem

> ◌ changeset: 56:81ae6b434ad6 > │ user:Uwe Brauer > │ date:Tue Dec 29 17:34:22 2020 +0100 > │ obsolete:pruned > │ summary: First version 56 was pruned, so all its descendants became orphans, ... > hg debugwhyunstable 57 > orphan: obsolete parent

Re: repository with subrespository: I am stuck with a nested nested path problem

> Which indicates that something is wrong I assume you at some point changed the default log template for some reason and this is why it doesn't actually tell what is wrong with the changesets (they're orphan). Try hg log -G -T default and hg debugwhyunstable.

Evolve mini-sprint January 7th

Hello everyone, Keeping the tradition of monthly mini-sprints related to all things Mercurial, the next one will be dedicated to changeset evolution and evolve extension (topic extension too). It will be held on Friday, January 7th. There's no specific schedule for the day, it will be open for

Evolve mini-sprint January 7th

Hello everyone, Keeping the tradition of monthly mini-sprints related to all things Mercurial, the next one will be dedicated to changeset evolution and evolve extension (topic extension too). It will be held on Friday, January 7th. There's no specific schedule for the day, it will be open for

Evolve mini-sprint January 7th

Hello everyone, Keeping the tradition of monthly mini-sprints related to all things Mercurial, the next one will be dedicated to changeset evolution and evolve extension (topic extension too). It will be held on Friday, January 7th. There's no specific schedule for the day, it will be open for

Evolve 10.4.1 released

involved: * Anton Shestakov * Sushil khanchi ## Evolve: 10.4.1 * compatibility with Mercurial 6.0 * documentation: add a help section about making evolve skip content-divergence check with experimental.evolution.allowdivergence. * documentation: mention that pick uses the active

Evolve 10.4.1 released

involved: * Anton Shestakov * Sushil khanchi ## Evolve: 10.4.1 * compatibility with Mercurial 6.0 * documentation: add a help section about making evolve skip content-divergence check with experimental.evolution.allowdivergence. * documentation: mention that pick uses the active

Re: small local feature branches? please help understand the workflow

> пт, 19 нояб. 2021 г. в 06:25, Victor Sudakov : > > I was unable to make it work. > > `pip3 install evolve --user` says that it is installed in > > /home/vas/.local/lib/python3.7/site-packages but mercurial says > > "failed to import extension evolve: No module named 'evolve'" Also, just

Re: small local feature branches? please help understand the workflow

пт, 19 нояб. 2021 г. в 06:25, Victor Sudakov : > I was unable to make it work. > `pip3 install evolve --user` says that it is installed in > /home/vas/.local/lib/python3.7/site-packages but mercurial says > "failed to import extension evolve: No module named 'evolve'" This is likely because your

Re: 5.9.3 Build Error

This issue was very recently brought up on our IRC, and the problem seems to be in setuptools, e.g. https://github.com/pypa/setuptools/issues/2849 The solution at the moment is to retry with setuptools 58.4. (Also, the person who knows more about this issue, Raphael, told me he can't send you a

Re: Evolve 10.4.0 released

On Sun, 17 Oct 2021 00:45:46 +0530 (IST) Faheem Mitha wrote: > 10.4.0 is currently not showing up in the tags for the Evolve repos at > https://www.mercurial-scm.org/repo/evolve/. The most recent version is > 10.3.3. This was unfortunately caused by a bug that made tag cache incorrect locally

Evolve 10.4.0 released

: * Anton Shestakov * Martin von Zweigbergk * Pierre-Yves David * Sushil khanchi ## Evolve: 10.4.0 * evolve: use a more stable criteria for picking p1 when solving content-divergence (most recent evolution will be used) * evolve: drop the deprecated --unstable, --divergent and --bumped

Evolve 10.4.0 released

: * Anton Shestakov * Martin von Zweigbergk * Pierre-Yves David * Sushil khanchi ## Evolve: 10.4.0 * evolve: use a more stable criteria for picking p1 when solving content-divergence (most recent evolution will be used) * evolve: drop the deprecated --unstable, --divergent and --bumped

Re: Evolve mini-sprint October 8th

Hello again, We have started the mini-sprint! As I've mentioned earlier, any questions about evolution are fine to ask either in our IRC (see the quoted email for links) or in the VC. Link to the VC: https://meet.jit.si/evolve-mini-sprint-10.4.0 Questions about Mercurial in general are also

Re: Evolve mini-sprint October 8th

Hello again, We have started the mini-sprint! As I've mentioned earlier, any questions about evolution are fine to ask either in our IRC (see the quoted email for links) or in the VC. Link to the VC: https://meet.jit.si/evolve-mini-sprint-10.4.0 Questions about Mercurial in general are also

Re: Evolve mini-sprint October 8th

Hello again, We have started the mini-sprint! As I've mentioned earlier, any questions about evolution are fine to ask either in our IRC (see the quoted email for links) or in the VC. Link to the VC: https://meet.jit.si/evolve-mini-sprint-10.4.0 Questions about Mercurial in general are also

Re: Evolve mini-sprint October 8th

Hello again, We have started the mini-sprint! As I've mentioned earlier, any questions about evolution are fine to ask either in our IRC (see the quoted email for links) or in the VC. Link to the VC: https://meet.jit.si/evolve-mini-sprint-10.4.0 Questions about Mercurial in general are also

Re: Evolve mini-sprint October 8th

On Wed, 29 Sep 2021 08:02:09 -0700 Martin von Zweigbergk via Mercurial-devel wrote: > I think organizing a "real" sprint in 10 days is not really realistic, > > though I agree that we should think about the next Mercurial sprint. > > > Do you know if anyone has started thinking about that?

Evolve mini-sprint October 8th

Hello everyone, Keeping the tradition of monthly mini-sprints related to all things Mercurial, the next one will be dedicated to changeset evolution and evolve extension (topic extension too). It will be held on Friday, October 8th. There's no specific schedule for the day, it will be open for

Evolve mini-sprint October 8th

Hello everyone, Keeping the tradition of monthly mini-sprints related to all things Mercurial, the next one will be dedicated to changeset evolution and evolve extension (topic extension too). It will be held on Friday, October 8th. There's no specific schedule for the day, it will be open for

Evolve mini-sprint October 8th

Hello everyone, Keeping the tradition of monthly mini-sprints related to all things Mercurial, the next one will be dedicated to changeset evolution and evolve extension (topic extension too). It will be held on Friday, October 8th. There's no specific schedule for the day, it will be open for

Re: can not install mercurial in a w10 PC

Just going to leave this link here: https://www.mercurial-scm.org/wiki/Python3 Apart from 3.5 through 3.9, Mercurial still supports 2.7 (although not sure if experimental Rust extensions are supported on 2.7). As already mentioned, python 2.6 is crazy old. I have no idea about anything windows,

Re: Rebase commit is not created if it was previously created then pruned

On Thu, 19 Aug 2021 00:23:26 -0400 Christopher Speck wrote: > The commit message cannot be modified to include additional noise for the > case I'm working on. I'm not familiar with extras, but that might be a way > to work around this. Does that require any further extension to be enabled >

Evolve 10.3.3 released

are: compatibility with Mercurial 5.9, and a bug that could lead to data loss when using evolve commands on a merge commit was fixed. See https://bz.mercurial-scm.org/show_bug.cgi?id=6416. Thanks to all the people involved: * Anton Shestakov * Martin von Zweigbergk * Matt Harbison * Pierre

Evolve 10.3.3 released

are: compatibility with Mercurial 5.9, and a bug that could lead to data loss when using evolve commands on a merge commit was fixed. See https://bz.mercurial-scm.org/show_bug.cgi?id=6416. Thanks to all the people involved: * Anton Shestakov * Martin von Zweigbergk * Matt Harbison * Pierre

D11223: obsolete: disable other evolution config options if createmarkers is off

av6 created this revision. Herald added a reviewer: hg-reviewers. Herald added a subscriber: mercurial-patches. REVISION SUMMARY We used to raise an abort in this case, but recent changes to local clone command (377d8fc20e34

D11221: rebase: use obsolete.isenabled() to check for experimental.allowdivergence

av6 created this revision. Herald added a reviewer: martinvonz. Herald added a reviewer: hg-reviewers. Herald added a subscriber: mercurial-patches. REVISION SUMMARY Now that obsolete.isenabled() can also check if divergence is allowed, let's use it for consistency. Other

D11222: fix: use obsolete.isenabled() to check for experimental.allowdivergence

av6 created this revision. Herald added a reviewer: hg-reviewers. Herald added a subscriber: mercurial-patches. REVISION SUMMARY Now that obsolete.isenabled() can also check if divergence is allowed, let's use it for consistency. Other experimental.evolution options are already checked via

Re: Rebase commit is not created if it was previously created then pruned

On Wed, 21 Jul 2021 16:41:56 -0400 Christopher Speck wrote: > I originally posted this in the Mercurial mailing list but found there’s a > separate one for Evolve. > > I’ve come across an issue while using the evolve extension where running a > `rebase` command unexpectedly does not result in

D10948: exchange: use "served" repo filter to guess what the server will publish

av6 created this revision. Herald added a reviewer: hg-reviewers. Herald added a subscriber: mercurial-patches. REVISION SUMMARY Previously, the second push in the added test would say "push would publish 2 changesets" because _checkpublish() was considering secret changesets to be

  1   2   3   4   5   6   >