-
Notifications
You must be signed in to change notification settings - Fork 68
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
Reflow: break lines at end of sentence / 80 cols #495
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good. I verified the following:
- The generated PDF has no unexpected differences vs. the main branch. (The only differences are the date and commit ID on the title page.)
- The script changes in this PR are identical to those in Run reflow #481, which were already reviewed.
Merging as editorial |
@@ -0,0 +1,7 @@ | |||
#!/usr/bin/python3 -i | |||
# | |||
# Copyright (c) 2018-2019 Collabora, Ltd. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Copyright 2023 The Khronos Group Inc.?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, that seems weird since the implementation of the Python package is copyright Khronos. I created a new __init__.py
file in #558.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks, and yes copy / pasted from Vulkan (https://github.com/KhronosGroup/Vulkan-Docs/blob/master/scripts/spec_tools/__init__.py)
@@ -0,0 +1,454 @@ | |||
#!/usr/bin/python3 -i | |||
# | |||
# Copyright 2013-2023 The Khronos Group Inc. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
2013-2023 -> just 2023?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I assume that @TApplencourt started by copying the "conventions.py" file from the Vulkan repo, which has this copyright date range. Since this file is a derived work, I think it's correct to keep the original date range.
Run Reflow, rebased from master
Run Reflow, rebased from master (cherry picked from commit e859ef7)
Run Reflow, rebased from master (cherry picked from commit e859ef7)
Follow up of #481 Rebase from master ( 463a26c )