-
Notifications
You must be signed in to change notification settings - Fork 3
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.27 #4179
Comments
Branch: 4179_cleanup |
|
|
|
|
mc-4179-fix-lto-type-mismatch-warning.patch: applied.
Thanks! |
|
|
|
|
|
mc-4179-chattr.c-fix-cast-qual-warning.patch: applied.
Thanks!
Branch: 4179_cleanup |
|
|
|
|
mc-4179-input.c-fix-cast-qual-warning.patch, |
|
|
I think the following patch is more simple: diff --git a/src/background.c b/src/background.c
index 584cd74ef..b5c64a5d0 100644
--- a/src/background.c
+++ b/src/background.c
@@ -281,10 +281,10 @@ background_attention (int fd, void *closure)
if (to_child_fd == -1)
message (D_ERROR, background_process_error, "%s", _("Unknown error in child"));
-
- /* Handle the call */
- if (type == Return_Integer)
+ else if (type == Return_Integer)
{
+ /* Handle the call */
+
int result = 0;
if (have_ctx == 0)
I think the test
in edit_do_search() can be just removed or replaced with assert to catch such case (can it occurs?). |
yes, your approach is more nice and simple. :) |
|
|
|
|
mc-4179-cid-background.c-fix-argument-cannot-be-negative.patch: done |
|
|
|
|
|
mc-4179-cid-dir.c-fix-resource-leak.patch: done |
done
done
skipped
done
done
done |
Important
This issue was migrated from Trac:
zaytsev
(@zyv)Note
Original attachments:
and
onMar 9, 2021 at 15:00 UTC
and
onMar 9, 2021 at 15:00 UTC
and
onMar 9, 2021 at 15:00 UTC
and
onMar 9, 2021 at 15:00 UTC
and
onMar 14, 2021 at 17:09 UTC
and
onMar 14, 2021 at 17:09 UTC
and
onMar 14, 2021 at 17:09 UTC
and
onMar 14, 2021 at 17:09 UTC
and
onMar 27, 2021 at 15:48 UTC
and
onMar 27, 2021 at 15:48 UTC
and
onMar 27, 2021 at 15:49 UTC
and
onMar 27, 2021 at 15:49 UTC
and
onMay 18, 2021 at 17:35 UTC
and
onMay 18, 2021 at 17:35 UTC
and
onMay 24, 2021 at 17:15 UTC
and
onMay 24, 2021 at 17:15 UTC
and
onMay 24, 2021 at 17:15 UTC
and
onMay 24, 2021 at 17:15 UTC
and
onMay 30, 2021 at 14:42 UTC
and
onMay 30, 2021 at 14:42 UTC
and
onMay 30, 2021 at 14:42 UTC
and
onMay 30, 2021 at 14:42 UTC
and
onMay 30, 2021 at 14:42 UTC
The text was updated successfully, but these errors were encountered: