docs: clarify project scope#93
Closed
a-rookie-of-C-language wants to merge 1 commit into
Closed
Conversation
Contributor
|
It looks like #60,you can add more information to that |
Contributor
Author
|
似乎你已经完成了这个pr,抱歉我并没有注意到,我现在就将其关闭 |
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.
#56
Summary
Clarifies the project scope for utilities outside GNU coreutils.
The README now has a short scope note, while CONTRIBUTING.md contains the fuller guidance for contributors. This captures the boundary discussed in the issue: small, commonly available, script-friendly Windows-native commands may be acceptable, while larger interactive tools such as
topare out of scope for now.