Ensure man1 POD files start with openssl- #10000
Closed
Conversation
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
Contributor
Author
|
Whee! Lucky 10K !!!!! |
Member
|
As a side note I notice that some of the man7 look like we might want to prefix them with openssl...or at least we seem to be polluting the man namespace with names like "property", "provider", "ct" etc. |
t8m
approved these changes
Sep 24, 2019
levitte
approved these changes
Sep 24, 2019
Member
|
I wondered who'd get the 10k 😅 |
Contributor
Author
|
ready for merge. |
Member
|
merged to master as a6dd3a3 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Commit b6b6657 (PR #9679) renamed most POD files. This change causes
find-doc-nits to flag misnamed files.
Also fix the two misnamed files that it found.
This should not be backported.