-
Notifications
You must be signed in to change notification settings - Fork 22
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
UCO Issues 562, 586, 590: Bump UCO to current state of develop-2.0.0 #155
Conversation
No effects were observed on Make-managed files. References: * ucoProject/UCO#586 * ucoProject/UCO#590 Signed-off-by: Alex Nelson <[email protected]>
UCO Issues 586, 590: Bump UCO to current state of develop
No effects were observed on Make-managed files. References: * ucoProject/UCO#586 * ucoProject/UCO#609 Signed-off-by: Alex Nelson <[email protected]>
UCO Issue 586: Bump UCO to current state of `develop`
No effects were observed on Make-managed files. References: * ucoProject/UCO#562 * ucoProject/UCO#586 * ucoProject/UCO#590 Signed-off-by: Alex Nelson <[email protected]>
This PR is ready for review and merge. |
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.
Assuming this merge doesn't include changes that have not yet been reviewed, the merge is approved.
In order to allow @ajnelson-nist to falsify this assumption, I'll leave the actual merge to him (providing such is allowed by our rules of conduct).
@plbt5 Our 2-key protocol is the submitter doesn't typically merge. This leaves 2-key easier to see in the Git history offline from GitHub. |
This PR does not require committee processing for merging. It should pass CI and receive an approving review, though.
This PR is part of delivering UCO Issues 562, 586, and 590 via the CASE website.
This PR also catches CASE's
develop-2.0.0
up withdevelop
, including handling Git submodule logistics.