Skip to content
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

Update copyright #326

Merged
merged 4 commits into from
Dec 18, 2023
Merged

Update copyright #326

merged 4 commits into from
Dec 18, 2023

Conversation

muzimuzhi
Copy link
Contributor

@muzimuzhi muzimuzhi commented Dec 14, 2023

Currently this PR give "Yes" and "Yes""No" (see #325 (comment)) to the questions I asked in #325.

Questions:

  • Is it ok to add 2023 to copyright notices to all l3build*.lua files even if some of them are not updated in 2023?
  • Does l3build want to keep precise copyright year lists, like
    File l3build-help.lua Copyright (C) 2018,2020,2021 The LaTeX Project

Closes #325

- Historic year lists are kept.
- Year 2022 is added when corresponding file is updated in that year.
Use a file specific single range.
@muzimuzhi muzimuzhi marked this pull request as ready for review December 14, 2023 21:38
@muzimuzhi
Copy link
Contributor Author

With the single range copyright, lua code used to update copyright can be simplified too.

@josephwright josephwright merged commit 5d99fcc into latex3:main Dec 18, 2023
1 check passed
@muzimuzhi muzimuzhi deleted the update-copyright branch December 18, 2023 16:40
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.

Copyright: update manually or automatically by update_tag()?
2 participants