chore(fileindex): strip upstream references from code comments#646
Merged
Conversation
Two comments introduced in #644's fix named an upstream project / its source symbol. Yarilo is its own product — such references belong in commits, PRs and docs, not in // comments. Reword to describe the mechanism (inode+device identity check; re-fetching the header after a log rotation) without the attribution. No behaviour change.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up cleanup after #645. Two comments added in that PR named an upstream project and one of its source symbols; per yarilo's own-product convention such references live in commits/PRs/docs, not in
//comments. Reworded to describe the mechanism (inode+device identity check; re-fetching the header after a log rotation) with no attribution and no behaviour change. appVersion → 2.1.12.