Fix additional libarchive comment typos - #685
Closed
gshaowei6 wants to merge 1 commit into
Closed
Conversation
gshaowei6
force-pushed
the
gshaowei6/cosmetic-typo-bounty-20260525
branch
from
May 25, 2026 15:04
0f463cc to
f23c927
Compare
Member
|
Thanks for the attention, but we are deliberately not making cosmetic changes to libarchive code, to minimize diffs to libarchive upstream. I made some of those fixes to https://github.com/libarchive/libarchive/ a few years ago; please send any further fixes for libarchive code to them. |
Author
|
Thanks for clarifying the maintenance policy. I will close this PR rather than keeping a cosmetic libarchive-vendored diff open in Tarsnap. If I pursue these remaining typo fixes, I will send them to |
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
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.
Summary:
Tests:
Related to #684.