[PATCH 1 of 2 stable] docs: remove link to Bitbucket source mirror

# HG changeset patch # User Manuel Jacob # Date 1600197859 -7200 # Tue Sep 15 21:24:19 2020 +0200 # Branch stable # Node ID 3124c863cd9eb9959896e8abeef2c08839844319 # Parent 0bca9e828db247730518cbb4fd9225ea42592faf # EXP-Topic bitbucket_references docs: remove link to Bitbucket source

[PATCH 2 of 2 stable] docs: note that the old issue tracker doesn’t work anymore

# HG changeset patch # User Manuel Jacob # Date 1600198226 -7200 # Tue Sep 15 21:30:26 2020 +0200 # Branch stable # Node ID d7b9dc92f3c0f85c87e8962bcc3fdca103670d03 # Parent 3124c863cd9eb9959896e8abeef2c08839844319 # EXP-Topic bitbucket_references docs: note that the old issue tracker

[PATCH stable] vcs: use correct name of parameter “reverse” in docstring of get_changesets()

# HG changeset patch # User Manuel Jacob # Date 1645849430 -3600 # Sat Feb 26 05:23:50 2022 +0100 # Branch stable # Node ID 2ea1e41d5d870cf3e2333ae541408129b5494120 # Parent 397f73d1cdd4b39c9c17bb8d45592e866fcab88c vcs: use correct name of parameter “reverse” in docstring of get_changesets

[PATCH stable] controllers: don’t pass start=0 to BaseRepository.get_changesets()

# HG changeset patch # User Manuel Jacob # Date 1645822846 -3600 # Fri Feb 25 22:00:46 2022 +0100 # Branch stable # Node ID 397f73d1cdd4b39c9c17bb8d45592e866fcab88c # Parent 017595560fc1e0f2acc086c63ed5f8906011d77b controllers: don’t pass start=0 to BaseRepository.get_changesets

[PATCH stable] hg: use correct start / stop indices when slicing revisions

# HG changeset patch # User Manuel Jacob # Date 1645848272 -3600 # Sat Feb 26 05:04:32 2022 +0100 # Branch stable # Node ID 84c94153376698aa028c03dbad1fc0dcf6f081ed # Parent 397f73d1cdd4b39c9c17bb8d45592e866fcab88c hg: use correct start / stop indices when slicing revisions Previously

Transferring changeset approval status to rebased successors

Hi, In one project I’m working on, we do code review of single changesets in a feature branch (usually the changesets are quite small and on average more than 10 are submitted for review at the same time). We also use Mercurial’s changeset evolution quite heavily. Feature branches are

Re: Freshly cloned Kallithea repository is corrupt

On 17/04/2023 13.39, Mads Kiilerich wrote: Hi That seems to be a Mercurial 6.4 regression, introduced by 87f0155d68aa . Can you confirm, and will you follow up upstream? I can do that, but I would be interested in how you found out. /Mads On 17/04/2023 03:10, Manuel Jacob wrote: When I

[PATCH] hg: add settings to make repositories non-publishing or use changeset evolution

# HG changeset patch # User Manuel Jacob # Date 1681995256 -7200 # Thu Apr 20 14:54:16 2023 +0200 # Node ID 56aad162afcff89ec7e0b8cc7a60fff2bbde6ec1 # Parent 294f5a6814edc267c87a77dad5131c08a50fae1c # EXP-Topic non_publishing_changeset_evolution hg: add settings to make repositories non

Re: [PATCH 1 of 2 stable v3] tests: set Git author and committer name and email settings explicitly

On 20/04/2023 11.19, Mads Kiilerich wrote: On 20/04/2023 01:30, Manuel Jacob wrote: On 20/04/2023 01.07, Mads Kiilerich wrote: Thanks - this looks much more approachable. But while processing v2 and our discussion and trying to give good input to what I would like to see in v3, I figured

[PATCH 1 of 2 stable v2] tests: set Git author and committer name and email settings explicitly

# HG changeset patch # User Manuel Jacob # Date 1680121377 -7200 # Wed Mar 29 22:22:57 2023 +0200 # Branch stable # Node ID 30082bb9719eb00f3be0081b7221d7c3061d4345 # Parent 0a9ddb8cd8c117671ecaf2b4126c3eef09e80ce8 # EXP-Topic tests-git tests: set Git author and committer name and email

[PATCH 2 of 2 stable v2] tests: prevent Git system and global configuration from loading

# HG changeset patch # User Manuel Jacob # Date 1680139355 -7200 # Thu Mar 30 03:22:35 2023 +0200 # Branch stable # Node ID e5251abd0a3c677d7bb0828f3a744789bd6fe4cb # Parent 30082bb9719eb00f3be0081b7221d7c3061d4345 # EXP-Topic tests-git tests: prevent Git system and global configuration

Re: [PATCH 2 of 2 stable v2] tests: prevent Git system and global configuration from loading

On 19/04/2023 14.27, Mads Kiilerich wrote: On 18/04/2023 20:35, Manuel Jacob wrote: # HG changeset patch # User Manuel Jacob # Date 1680139355 -7200 #  Thu Mar 30 03:22:35 2023 +0200 # Branch stable # Node ID e5251abd0a3c677d7bb0828f3a744789bd6fe4cb # Parent

Re: [PATCH 2 of 2 stable v2] tests: prevent Git system and global configuration from loading

On 19/04/2023 16.27, Mads Kiilerich wrote: On 19/04/2023 15:14, Manuel Jacob wrote: On 19/04/2023 14.27, Mads Kiilerich wrote: On 18/04/2023 20:35, Manuel Jacob wrote: ... I think this changeset should come first. As you say, it makes the test work the same way everywhere. user.useconfigonly

Re: [PATCH 2 of 2 stable v2] tests: prevent Git system and global configuration from loading

On 19/04/2023 17.21, Manuel Jacob wrote: On 19/04/2023 16.27, Mads Kiilerich wrote: On 19/04/2023 15:14, Manuel Jacob wrote: On 19/04/2023 14.27, Mads Kiilerich wrote: On 18/04/2023 20:35, Manuel Jacob wrote: ... I think this changeset should come first. As you say, it makes the test work

Re: [PATCH 2 of 2 stable v2] tests: prevent Git system and global configuration from loading

On 19/04/2023 19.12, Mads Kiilerich wrote: On 19/04/2023 17:27, Manuel Jacob wrote: On 19/04/2023 17.21, Manuel Jacob wrote: On Arch Linux: % git --version git version 2.40.0 % GIT_CONFIG_GLOBAL=/dev/null GIT_CONFIG_SYSTEM=/dev/null EMAIL='foo@bar' git commit -m "committed new 0"

[PATCH 2 of 2 stable v3] tests: prevent Git system and global configuration from loading

# HG changeset patch # User Manuel Jacob # Date 1680139355 -7200 # Thu Mar 30 03:22:35 2023 +0200 # Branch stable # Node ID e9a574cea28a8db42ff6a84a41a91b6cbe336cbc # Parent 846ca7f28bd40e07c76ed259ce96a31a85d0c4ea # EXP-Topic tests-git tests: prevent Git system and global configuration

[PATCH 1 of 2 stable v3] tests: set Git author and committer name and email settings explicitly

# HG changeset patch # User Manuel Jacob # Date 1680121377 -7200 # Wed Mar 29 22:22:57 2023 +0200 # Branch stable # Node ID 846ca7f28bd40e07c76ed259ce96a31a85d0c4ea # Parent 0a9ddb8cd8c117671ecaf2b4126c3eef09e80ce8 # EXP-Topic tests-git tests: set Git author and committer name and email

Re: [PATCH 1 of 2 stable v3] tests: set Git author and committer name and email settings explicitly

are equivalently good). My changeset description is a bit more extensive. I’ll let you decide if merging the two patches is worth the effort in case you decide for your implementation. /Mads On 20/04/2023 00:39, Manuel Jacob wrote: # HG changeset patch # User Manuel Jacob # Date 1680121377

Freshly cloned Kallithea repository is corrupt

When I cloned the Kallithea repository, it was corrupted. % hg clone https://kallithea-scm.org/repos/kallithea /tmp/kallithea applying clone bundle from https://kallithea-scm.org/bundles/kallithea-b103f41a4954e2814dc547671771bdeebc1f80be.bzip2-v1.hg adding changesets adding manifests adding

[PATCH 1 of 2] tests: set Git author and committer name and email settings explicitly

# HG changeset patch # User Manuel Jacob # Date 1680121377 -7200 # Wed Mar 29 22:22:57 2023 +0200 # Node ID 2304f8da62b03f6cfd966b72eec70c38c4d52e37 # Parent 7037365a7bc351b81f05c790c6d3417d81d7bd5d # EXP-Topic tests-git tests: set Git author and committer name and email settings explicitly

[PATCH 2 of 2] tests: prevent Git system and global configuration from loading

# HG changeset patch # User Manuel Jacob # Date 1680139355 -7200 # Thu Mar 30 03:22:35 2023 +0200 # Node ID 4933600c49883dfc142f97a32dd08f9dd82b0d31 # Parent 2304f8da62b03f6cfd966b72eec70c38c4d52e37 # EXP-Topic tests-git tests: prevent Git system and global configuration from loading

Re: [PATCH 2 of 2] tests: prevent Git system and global configuration from loading

On 31/03/2023 20.45, Mads Kiilerich wrote: On 30/03/2023 03:37, Manuel Jacob wrote: # HG changeset patch # User Manuel Jacob # Date 1680139355 -7200 #  Thu Mar 30 03:22:35 2023 +0200 # Node ID 4933600c49883dfc142f97a32dd08f9dd82b0d31 # Parent  2304f8da62b03f6cfd966b72eec70c38c4d52e37 # EXP

Re: Transferring changeset approval status to rebased successors

requests would continue to work exactly as they do now. /Mads On 25/03/2023 22:10, Manuel Jacob wrote: Hi, In one project I’m working on, we do code review of single changesets in a feature branch (usually the changesets are quite small and on average more than 10 are submitted for review

[PATCH] api: include creation date in comments

# HG changeset patch # User Manuel Jacob # Date 1680087692 -7200 # Wed Mar 29 13:01:32 2023 +0200 # Node ID 44e34dcb73b1d1cf6a7527094521ab97968d8396 # Parent d2166e7ea65797fdccb548cd9cf416c8ed02fc6b # EXP-Topic api-comments api: include creation date in comments diff --git a/kallithea

[PATCH 1 of 2] api: fix get_changeset() when incomplete raw_id is passed with with_reviews

# HG changeset patch # User Manuel Jacob # Date 1680080700 -7200 # Wed Mar 29 11:05:00 2023 +0200 # Node ID 2704d3ca4210e14e559b2a1f23dacdd988989533 # Parent 7037365a7bc351b81f05c790c6d3417d81d7bd5d # EXP-Topic api-comments api: fix get_changeset() when incomplete raw_id is passed

[PATCH 2 of 2] api: add possibility to optionally return comments from get_changeset()

# HG changeset patch # User Manuel Jacob # Date 1680083947 -7200 # Wed Mar 29 11:59:07 2023 +0200 # Node ID d2166e7ea65797fdccb548cd9cf416c8ed02fc6b # Parent 2704d3ca4210e14e559b2a1f23dacdd988989533 # EXP-Topic api-comments api: add possibility to optionally return comments from