| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | extract tor_async_utils::oneshot into ::oneshot-fused-workaround | Jim Newsome | 2024-08-28 | 1 | -1/+1 |
| | | | | | | | | | | | | | | | Having this in the `tor-async-utils` crate prevents us from doing both of the following without introducing a circular dependency: * using it in `tor-rtmock` (which we currently do, particularly in tests). * using `tor-rtmock` to test things in `tor-async-utils`. We don't do this yet, but it is generally sensible to do so. In particular we want to move the `stream_peak` module there, which is currently tested with `tor-rtmock`. Moving this into its own crate avoids this circular dependency. | ||||
| * | tor-ptmgr: added a 'managed-pts' default feature | Steven Engler | 2024-08-21 | 1 | -3/+0 |
| | | | | | | This conditionally compiles most of the code related to managed transports. | ||||
| * | tor-ptmgr: move some code to a new 'managed' module | Steven Engler | 2024-08-20 | 1 | -0/+319 |
| Code that's related to managed transports has been moved to a new 'managed' module. This includes the PT reactor since it's not needed for unmanaged transports. | |||||
