- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 5
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
Prepare for release mc-4.8.30 #4426
Comments
|
Branch: 4426_cleanup |
|
mc-4426-fix-implicit-function-declaration-warning.patch: applied.
Branch: 4426_cleanup |
Branch: 4426_cleanup |
|
Added patch from closed GitHub PR. |
pr-164-add-dylib-support.patch: applied. |
|
|
Two more trivial patches from GitHub added. |
pr-182-syntax-update-1.patch: applied |
|
Added a patch from GitHub to highlight *.zsh files as shell scripts. |
pr-168.patch: applied. |
Got two warnings during the build on master:
|
Built and pushed rc1 tarball. We really need to do something about Travis now :( noticed that CI hasn't been run since January... |
Replying to zaytsev:
Will be fixed in the next cleanup after release. |
|
I've got reply from support and hopefully Travis builds will be working again, but now it complains about 1) warnings and 2) indentation. See screenshot. |
I don't want modify the code from GNU tar and gnulib to pacify GCC. What about of use
in tar-sparse.c? |
Well, one could try to send a path to tar and gnulib people, but if you can't be bothered, then I think a pragma is OK to silence warnings for stolen code. If we start modifying it again, then updating will become more difficult... I think that it was quite a lot of work for you already to bring our tar implementation up to date. |
done
done
|
Important
This issue was migrated from Trac:
zaytsev
(@zyv)Note
Original attachments:
zaytsev
(@zyv) onJan 14, 2023 at 19:35 UTC
and
onMar 3, 2023 at 13:47 UTC
zaytsev
(@zyv) onMay 21, 2023 at 14:47 UTC
zaytsev
(@zyv) onMay 22, 2023 at 6:13 UTC
zaytsev
(@zyv) onMay 22, 2023 at 6:13 UTC
zaytsev
(@zyv) onMay 28, 2023 at 16:04 UTC
zaytsev
(@zyv) onAug 7, 2023 at 15:24 UTC
The text was updated successfully, but these errors were encountered: