Move tor-specific code from `chutney.TorNet` to new subpackage `chutney.tor`
1 unresolved thread
chutney.TorNet
is already large enough to warrant splitting up, and we want to establish a pattern such that the new arti-specific code will likewise go in a new subpackage instead of into chutney.TorNet
Progress on #40030
Merge request reports
Activity
assigned to @jnewsome
mentioned in issue #40030
added Project 141 label
requested review from @nickm
added 1 commit
- da5f8985 - Move error types to new package chutney.errors
added 1 commit
- 6a3e7a25 - fixup! Move error types to new package chutney.errors
marked this merge request as draft from jnewsome/chutney@6a3e7a25
added 10 commits
-
6a3e7a25...6631238e - 5 commits from branch
tpo/core:main
- 647f89f7 - Create a package chutney.tor and move chutney.torrc there
- 612fdc93 - TorNet.Node: store controller as base class NodeController
- 8b68d853 - Move LocalController to new package chutney.tor.controller
- 2e03b657 - Move LocalBuilder to new package chutney.tor.builder
- a2dcea7a - Move error types to new package chutney.errors
Toggle commit list-
6a3e7a25...6631238e - 5 commits from branch
added 7 commits
-
e110f486...b2fe99e3 - 2 commits from branch
tpo/core:main
- dc4651cf - Create a package chutney.tor and move chutney.torrc there
- 2a53c834 - TorNet.Node: store controller as base class NodeController
- 8d634e62 - Move LocalController to new package chutney.tor.controller
- 95609d70 - Move LocalBuilder to new package chutney.tor.builder
- 57c49781 - Move error types to new package chutney.errors
Toggle commit list-
e110f486...b2fe99e3 - 2 commits from branch
enabled an automatic merge when all merge checks for 57c49781 pass
mentioned in commit cd5237a7
Please register or sign in to reply