-
Notifications
You must be signed in to change notification settings - Fork 386
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
Small cleanups + one bug fix #2718
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.
LGTM, considering podman 5.5 is set be released in early may I think we can ignore f40 (go 1.22) for it which means we could consider updating to go 1.23 in this release cycle if there is anything specific you would like to take advantage off.
(I keep branches containers/skopeo@main...mtrmac:skopeo:go1.23 and mtrmac/image@cleanups...mtrmac:image:go1.23 around, but that’s all code cleanups and rushing to apply them would not benefit users — I think the primary reason to move to Go 1.23 would be to catch up to some dependencies.) |
Yes right, there are a few go 1.23 deps already so we should update sooner than later unless someone sees a strong reason why we shouldn't. |
Microoptimize the success case. Should not change behavior. Signed-off-by: Miloslav Trmač <[email protected]>
Don't update only a private copy of the element. Signed-off-by: Miloslav Trmač <[email protected]>
Should not change (test) behavior. Signed-off-by: Miloslav Trmač <[email protected]>
Should not change behavior. Signed-off-by: Miloslav Trmač <[email protected]>
Should not change behavior. Signed-off-by: Miloslav Trmač <[email protected]>
Should not change behavior. Signed-off-by: Miloslav Trmač <[email protected]>
… discovered while looking at for opportunities to benefit from new features of Go 1.23 and Go 1.24, hence a fairly random collection.
See individual commit messages for details.