remove EXTNID_MIGTD_EVENT_LOG_INIT
Maintainers usually reply within 2 days
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 72/100
Research direction
The payload names no file, so start by searching the repository for EXTNID_MIGTD_EVENT_LOG_INIT to find its definition and any remaining references. Confirm nothing still uses it, then remove the constant and any dead code around it. Done means the identifier no longer appears in the tree and cargo build and cargo test still pass.
Written by the indexing model from the issue text.
Description
It is no longer used.
- Dominant language
- Rust
- Stars
- 58
- Forks
- 43
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 41
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from intel/MigTD
-
MigTD should check SVN2 == SVNPossibly taken @MichalTarnacki claimed this 2 days ago. Open
Difficulty 3/5 Half a day Newbie friendliness 48/100
intel/MigTD#1093 · 1 assignee ·
Maintainers usually reply within 2 days
-
Difficulty 3/5 Half a day Newbie friendliness 55/100
intel/MigTD#1092 · 1 comment ·
Maintainers usually reply within 2 days
-
consider removing policy SVN checkPossibly taken @MichalTarnacki claimed this 2 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 45/100
intel/MigTD#1091 · 1 comment · 1 assignee ·
Maintainers usually reply within 2 days
-
Support non-zero SERVTD_ATTR?Possibly taken @jyao1 claimed this 15 days ago. Open
intel/MigTD#1086 · 1 assignee ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 1-2 days Newbie friendliness 38/100
intel/MigTD#1076 · 2 comments ·
Maintainers usually reply within 2 days
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
max-sixty/worktrunk#4727 · 7 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
follow-up
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
carrick-sh/carrick#1859 ·
Maintainers usually reply within 1 day
-
crate: spate-kafka documentation priority: medium
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Maintainers usually reply within 1 day