transporter cleanup / patch #4246
Comments
vexed uploaded file for master |
vexed uploaded file bugfixes/3.1 |
vexed uploaded file needs the other patches applied first. |
stiv commented Amazing how one little func makes the code so much prettier. Don't see anything obviously wrong a first glance. If it compiles, ship it! |
Per commented Looks good to me. |
vexed changed status from |
vexed changed owner from `` to |
vexed changed resolution from `` to |
vexed committed [93] In Warzone2100/warzone2100@93c18a2:
|
vexed commented In Warzone2100/warzone2100@c36361b:
|
vexed committed [99] In Warzone2100/warzone2100@99b8218:
|
vexed committed [201] In Warzone2100/warzone2100@201dc76:
|
resolution_fixed
type_patch (an actual patch, not a request for one)
| by vexedCleaning up all these things to make it less error prone.
No logic should have changed at all, if it did, then it is an error.
The transporter fix patch obviously needs the other patch first.
Would be nice to gets some extra set of eyes on this, in case I missed something.
Issue migrated from trac:4246 at 2022-04-16 11:46:41 -0700
The text was updated successfully, but these errors were encountered: