Repository navigation
Revert "LICENSE: a copy in every module" (#6) - #7
Merged
Merged
Conversation
…its own directory" It was not true. When a nested module has no LICENSE of its own, the go command puts the repository root's in its zip, so these modules already carried one. The copies added nothing but a second file to keep in step. This reverts #6. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
1 participant
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.
#6 을 되돌립니다. 전제가 틀렸습니다 — 하위 모듈 디렉터리에 LICENSE 가 없으면 go 명령이 레포 루트의 LICENSE 를 그 모듈 zip 에 넣어 줍니다 (예:
mkot/otlp@v0.0.0-20261013182918의 zip 에 LICENSE 가 이미 있음). 복사본은 같은 파일을 하나 더 관리하게 할 뿐이었습니다.🤖 Generated with Claude Code