Fri, 02 Dec 2022 02:03:49 +0100 changelog-v2: fix the docket `struct`
Pierre-Yves David <pierre-yves.david@octobus.net> [Fri, 02 Dec 2022 02:03:49 +0100] rev 49714
changelog-v2: fix the docket `struct` The previous definition used `L` which is actually 4 bytes, while the documentation and intend was to use `Q`, i.e. 8 bytes.
Thu, 01 Dec 2022 02:26:34 +0100 path: pass `path` to `peer` in infinite push
Pierre-Yves David <pierre-yves.david@octobus.net> [Thu, 01 Dec 2022 02:26:34 +0100] rev 49713
path: pass `path` to `peer` in infinite push We directly use the `path` object to build the `peer` object.
Thu, 01 Dec 2022 02:21:18 +0100 path: pass `path` to `peer` in `hg histedit`
Pierre-Yves David <pierre-yves.david@octobus.net> [Thu, 01 Dec 2022 02:21:18 +0100] rev 49712
path: pass `path` to `peer` in `hg histedit` We directly use the `path` object to build the `peer` object.
Thu, 01 Dec 2022 02:14:40 +0100 path: pass `path` to `peer` in the `outgoing` revset
Pierre-Yves David <pierre-yves.david@octobus.net> [Thu, 01 Dec 2022 02:14:40 +0100] rev 49711
path: pass `path` to `peer` in the `outgoing` revset We directly use the `path` object to build the `peer` object.
Thu, 01 Dec 2022 02:11:21 +0100 path: pass `path` to `peer` in `hg summary`
Pierre-Yves David <pierre-yves.david@octobus.net> [Thu, 01 Dec 2022 02:11:21 +0100] rev 49710
path: pass `path` to `peer` in `hg summary` We directly use the `path` object to build the `peer` object.
Thu, 01 Dec 2022 02:09:43 +0100 path: pass `path` to `peer` in `hg outgoing`
Pierre-Yves David <pierre-yves.david@octobus.net> [Thu, 01 Dec 2022 02:09:43 +0100] rev 49709
path: pass `path` to `peer` in `hg outgoing` We directly use the `path` object to build the `peer` object.
Thu, 01 Dec 2022 01:57:14 +0100 path: pass `path` to `peer` in `hg bundle`
Pierre-Yves David <pierre-yves.david@octobus.net> [Thu, 01 Dec 2022 01:57:14 +0100] rev 49708
path: pass `path` to `peer` in `hg bundle` We directly use the `path` object to build the `peer` object.
Wed, 30 Nov 2022 19:43:26 +0100 path: have `peer` constructor accept a `path` object
Pierre-Yves David <pierre-yves.david@octobus.net> [Wed, 30 Nov 2022 19:43:26 +0100] rev 49707
path: have `peer` constructor accept a `path` object We don't do anything fancy with it yet, but this is an important step towards having the peers aware of their "source" and associated configurations.
Thu, 01 Dec 2022 01:46:46 +0100 path: deprecated the `pushloc` attribute
Pierre-Yves David <pierre-yves.david@octobus.net> [Thu, 01 Dec 2022 01:46:46 +0100] rev 49706
path: deprecated the `pushloc` attribute We want to make sure people with use the full featured path "variant".
Thu, 01 Dec 2022 01:41:34 +0100 path: update logic in `perf` to use the push variant when available
Pierre-Yves David <pierre-yves.david@octobus.net> [Thu, 01 Dec 2022 01:41:34 +0100] rev 49705
path: update logic in `perf` to use the push variant when available The command seems currently broken, but at least it won't be broken by us !
Thu, 01 Dec 2022 01:38:33 +0100 path: directly use the push_variant in `infinitepush`
Pierre-Yves David <pierre-yves.david@octobus.net> [Thu, 01 Dec 2022 01:38:33 +0100] rev 49704
path: directly use the push_variant in `infinitepush` We don't need any extra processing now.
Thu, 01 Dec 2022 01:38:07 +0100 path: directly use the push_variant in `hg histedit` outgoing logic
Pierre-Yves David <pierre-yves.david@octobus.net> [Thu, 01 Dec 2022 01:38:07 +0100] rev 49703
path: directly use the push_variant in `hg histedit` outgoing logic We don't need any extra processing now.
Thu, 01 Dec 2022 01:37:41 +0100 path: directly use the push_variant in the `outgoing` revset
Pierre-Yves David <pierre-yves.david@octobus.net> [Thu, 01 Dec 2022 01:37:41 +0100] rev 49702
path: directly use the push_variant in the `outgoing` revset We don't need any extra processing now.
Thu, 01 Dec 2022 01:37:10 +0100 path: directly use the push_variant in outgoing internals
Pierre-Yves David <pierre-yves.david@octobus.net> [Thu, 01 Dec 2022 01:37:10 +0100] rev 49701
path: directly use the push_variant in outgoing internals We don't need any extra processing now.
Thu, 01 Dec 2022 01:35:17 +0100 path: directly use the push_variant in `hg summary`
Pierre-Yves David <pierre-yves.david@octobus.net> [Thu, 01 Dec 2022 01:35:17 +0100] rev 49700
path: directly use the push_variant in `hg summary` We don't need any extra processing now.
Thu, 01 Dec 2022 01:34:58 +0100 path: directly use the push_variant in `hg outgoing`
Pierre-Yves David <pierre-yves.david@octobus.net> [Thu, 01 Dec 2022 01:34:58 +0100] rev 49699
path: directly use the push_variant in `hg outgoing` We don't need any extra processing now.
Thu, 01 Dec 2022 01:34:26 +0100 path: directly use the push_variant in `hg push`
Pierre-Yves David <pierre-yves.david@octobus.net> [Thu, 01 Dec 2022 01:34:26 +0100] rev 49698
path: directly use the push_variant in `hg push` We don't need any extra processing now.
Thu, 01 Dec 2022 01:33:27 +0100 path: have `get_push_paths` directly return the push variants
Pierre-Yves David <pierre-yves.david@octobus.net> [Thu, 01 Dec 2022 01:33:27 +0100] rev 49697
path: have `get_push_paths` directly return the push variants So the function directly returns usable paths, that should help the callers!
Thu, 01 Dec 2022 01:32:24 +0100 path: add a method to retrieve a "push variant" of a path
Pierre-Yves David <pierre-yves.david@octobus.net> [Thu, 01 Dec 2022 01:32:24 +0100] rev 49696
path: add a method to retrieve a "push variant" of a path This gets you the same path, but using the `pushurl` as destination. This opens the way for a lot of different improvements, the one which interests us is having `peer` objects aware of the `path` they came from.
Thu, 01 Dec 2022 18:01:24 +0400 tests: use an all too familiar executable in test-run-tests.t (issue6661) stable
Anton Shestakov <av6@dwimlabs.net> [Thu, 01 Dec 2022 18:01:24 +0400] rev 49695
tests: use an all too familiar executable in test-run-tests.t (issue6661) true(1) sometimes lives in /usr/bin/, and so this test fails on such systems. We also can't use which(1), because it's apparently not POSIX and Debian complains about it [1]. We also cannot really create a script and chmod +x it, because this is a symlink case, execbit case is slightly below. So let's use something that we know is executable, but not hg itself.
Thu, 01 Dec 2022 01:27:47 +0100 path: move the url parsing and related attribute setting to a method
Pierre-Yves David <pierre-yves.david@octobus.net> [Thu, 01 Dec 2022 01:27:47 +0100] rev 49694
path: move the url parsing and related attribute setting to a method This will make it simpler to reuse this logic in the next changeset.
Tue, 29 Nov 2022 22:22:18 +0100 peer-or-repo: remove the now unused function
Pierre-Yves David <pierre-yves.david@octobus.net> [Tue, 29 Nov 2022 22:22:18 +0100] rev 49693
peer-or-repo: remove the now unused function We do not need it anymore.
Tue, 29 Nov 2022 22:21:19 +0100 peer-or-repo: build a repo directly in the `repo` function
Pierre-Yves David <pierre-yves.david@octobus.net> [Tue, 29 Nov 2022 22:21:19 +0100] rev 49692
peer-or-repo: build a repo directly in the `repo` function We skip the ambiguous _peerorrepo function to explicitly build a repo within the dedicated function. The peer scheme are therefore no longer considered to build the object.
Tue, 29 Nov 2022 22:04:23 +0100 peer-or-repo: build a peer directly in the `peer` function
Pierre-Yves David <pierre-yves.david@octobus.net> [Tue, 29 Nov 2022 22:04:23 +0100] rev 49691
peer-or-repo: build a peer directly in the `peer` function We skip the ambiguous _peerorrepo function to explicitly build a peer within the dedicated function. This mean explicitly getting a peer from an explicitly create repository when necessary.
Tue, 29 Nov 2022 22:03:10 +0100 static-http: have `statichttprepo.instance` return a peer object
Pierre-Yves David <pierre-yves.david@octobus.net> [Tue, 29 Nov 2022 22:03:10 +0100] rev 49690
static-http: have `statichttprepo.instance` return a peer object It previously returned a statichttprepo object which could not be used for anything but creating a peer. So lets put it into the peer bucket with a peer behavior.
Wed, 30 Nov 2022 12:22:02 +0100 scheme: move the drive letter checking in its own function
Pierre-Yves David <pierre-yves.david@octobus.net> [Wed, 30 Nov 2022 12:22:02 +0100] rev 49689
scheme: move the drive letter checking in its own function This help the readability of the main function as is was taking much more room than the main logic.
Tue, 29 Nov 2022 21:48:08 +0100 peer-or-repo: split the scheme between repo and peer
Pierre-Yves David <pierre-yves.david@octobus.net> [Tue, 29 Nov 2022 21:48:08 +0100] rev 49688
peer-or-repo: split the scheme between repo and peer Some of the scheme will always produce a peer and some will always produce a repository. So lets use different mapping to reduce the ambiguity.
Wed, 30 Nov 2022 13:55:15 +0100 peer-or-repo: stop relying on AttributeError in `islocal`
Pierre-Yves David <pierre-yves.david@octobus.net> [Wed, 30 Nov 2022 13:55:15 +0100] rev 49687
peer-or-repo: stop relying on AttributeError in `islocal` This will confused pytypes in a future changeset.
Tue, 29 Nov 2022 21:42:08 +0100 repo-or-peer: deprecate calling `islocal` on non-path object
Pierre-Yves David <pierre-yves.david@octobus.net> [Tue, 29 Nov 2022 21:42:08 +0100] rev 49686
repo-or-peer: deprecate calling `islocal` on non-path object There object have a `.local()` method and should use it.
Thu, 01 Dec 2022 15:27:11 +0400 tests: add the missing space to test-hghave.t (issue6762) stable
Anton Shestakov <av6@dwimlabs.net> [Thu, 01 Dec 2022 15:27:11 +0400] rev 49685
tests: add the missing space to test-hghave.t (issue6762) log() in run-tests.py add a space to the end of all messages that it prints, and I missed this fact in my previous patch.
(0) -30000 -10000 -3000 -1000 -300 -100 -50 -30 +30 +50 +100 +300 +1000 tip