#18618 closed defect (duplicate)
Write a tool to move functions around from module to module
| Reported by: | nickm | Owned by: | nickm |
|---|---|---|---|
| Priority: | Medium | Milestone: | Tor: 0.2.9.x-final |
| Component: | Core Tor/Tor | Version: | |
| Severity: | Normal | Keywords: | TorCoreTeam201604, tor-modularity |
| Cc: | Actual Points: | ||
| Parent ID: | Points: | small/medium | |
| Reviewer: | Sponsor: | SponsorS-can |
Description
It's annoying to move code between modules, especially when doing a _bulk_ move, since you can't easily verify the move, and you can't easily review the move decision without reviewing huge patches.
I'm working on a tool to fix that by doing a two step annotate-then-move process.
Child Tickets
Change History (4)
comment:1 Changed 5 years ago by
| Owner: | set to nickm |
|---|---|
| Status: | new → accepted |
comment:2 Changed 5 years ago by
| Keywords: | TorCoreTeam201604 added |
|---|
comment:3 Changed 5 years ago by
| Resolution: | → duplicate |
|---|---|
| Status: | accepted → closed |
This is now merged into #18803.
comment:4 Changed 5 years ago by
| Keywords: | tor-modularity added |
|---|
Note: See
TracTickets for help on using
tickets.
These are infrastructure that will help out other projects, and should go in early. Marking them for April.