8000 Add the required `.` at the end of copyright lines. by jrvanwhy · Pull Request #3379 · tock/tock · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Add the required . at the end of copyright lines. #3379

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 24, 2023

Conversation

jrvanwhy
Copy link
Contributor

Pull Request Overview

When I implemented the license checker in #3345, I did not notice that trd-legal.md requires a period at the end of the copyright line. This PR adds that period to the license headers from #3345.

This begs the question: should I add logic to the license checker than checks the format of Copyright lines? I'm leaning towards "no" because they should be mostly copy-and-paste and minor punctuation errors don't seem very significant.

Documentation Updated

  • Updated the relevant files in /docs, or no updates are required.

Formatting

  • Ran make prepush.

When I implemented the license checker in tock#3345, I did not notice that `trd-legal.md` required a period (`.`) at the end of the copyright line. This PR adds that period to the license headers from tock#3345.

This begs the question: should I add logic to the license checker than checks the format of `Copyright` lines? I'm leaning towards "no" because they *should* be mostly copy-and-paste and it minor punctuation errors don't seem very significant.
@hudson-ayers
Copy link
Contributor

Re: your question, I also lean towards "no"

@jrvanwhy
Copy link
Contributor Author

bors r+

@bors
Copy link
Contributor
91AC bors bot commented Jan 24, 2023

@bors bors bot merged commit 0ce3945 into tock:master Jan 24, 2023
@jrvanwhy jrvanwhy deleted the copyright-fmt branch May 10, 2023 19:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
0