[PATCH] sv, runsv, svlogd: update to match version 2.1.2 of runit

up/down: 567/-171) Total: 396 bytes textdata bss dec hex filename 87135041582144 877652 d6454 busybox_old 87186741582144 878169 d6659 busybox_unstripped Signed-off-by: James Byrne <james.by...@origamienergy.com> --- runit/runsv.c

Resubmitting a patch

? Should I resubmit my patch and see if anyone notices this time, or is it enough just to draw attention to it? Thanks, James Byrne ___ busybox mailing list busybox@busybox.net http://lists.busybox.net/mailman/listinfo/busybox

Re: Resubmitting a patch

On 15/05/17 12:17, Daniel Thompson wrote: On 12/05/17 17:52, James Byrne wrote: Hi, I submitted a patch to this mailing list on December 15, 2016 which updated sv, runsv and svlogd by pulling in all the upstream changes and fixes to match version 2.1.2 of runit. I didn't receive any replies

Re: add bb_info_msg was Re: Applets send errors to syslog during normal, successful operation

On 11/03/18 21:37, Tito wrote: Deweloper's patch is smaller in code size and adds more features. This thread seems to have gone a bit cold since March, and in the meantime I have implemented my own patch (because I didn't notice this thread) which is very similar too, but slightly more

[PATCH 1/1] Optionally re-introduce bb_info_msg()

: 0/2 grow/shrink: 3/1 up/down: 12/-44)Total: -32 bytes textdata bss dec hex filename 93458042631856 940699 e5a9b busybox_old 93454942621856 940667 e5a7b busybox_unstripped Signed-off-by: James Byrne <james.by...@origamienergy.

[PATCH 1/1] libbb: reduce the overhead of single parameter bb_error_msg() calls

: 3/0 grow/shrink: 4/301 up/down: 73/-910)Total: -837 bytes textdata bss dec hex filename 93694942631856 943068 e63dc busybox_old 93609842631856 942217 e6089 busybox_unstripped Signed-off-by: James Byrne <james.by...@origamienergy.com> ---

Following-up bb_error_msg()/bb_info_msg() patches

the overhead of single parameter bb_error_msg() calls http://lists.busybox.net/pipermail/busybox/2018-May/086423.html Any feedback on these would be appreciated. Thanks, James Byrne The contents of this email and any attachment are confidential to the intended recipient(s). If you

[PATCH 1/1] wget: make --no-check-certificate option appear in usage

The line for this option was missing the 'usage:' prefix, meaning that it was ignored. Signed-off-by: James Byrne --- networking/wget.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/networking/wget.c b/networking/wget.c index 8103aac..b36c14a 100644 --- a/networking/wget.c

Re: [PATCH 1/1] wget: make --no-check-certificate option appear in usage

Hi Rafał, On 08/06/18 20:26, Rafał Miłecki wrote: This footer rather shouldn't be there. Various open source project were rejecting patches because of such texts. Yes, I know, it's a source of some annoyance to me too, but this is inserted by the outgoing SMTP server and I have no control

Re: [PATCH 1/1] libbb: reduce the overhead of single parameter bb_error_msg() calls

, James Byrne <james.by...@origamienergy.com> wrote: The space saving gained by this (using 'defconfig' on x86_64 with gcc Ubuntu 6.4.0-17ubuntu1~16.04) was: -- (add/remove: 3/0 grow/shrink: 4/301 up/down: 7

Following-up bb_info_msg() patch

it is not suitable so that I can rework it if necessary. Thanks, James Byrne -- The contents of this email and any attachment are confidential to the intended recipient(s). If you are not an intended recipient: (i) do not use, disclose, distribute, copy or publish this email or its contents; (ii) please

Patch follow-up: Optionally re-introduce bb_info_msg()

to reject it then it would be useful to know what they are, but not getting any response at all is a little discouraging. Thanks, James Byrne -- The contents of this email and any attachment are confidential to the intended recipient(s). If you are not an intended recipient: (i) do not use, disclose

[PATCH 1/1] Optionally re-introduce bb_info_msg()

/shrink: 3/1 up/down: 12/-48)Total: -36 bytes Signed-off-by: James Byrne --- Config.in| 9 +++ include/libbb.h | 9 ++- libbb/verror_msg.c | 22 ++-- loginutils/chpasswd.c| 2 +- loginutils/passwd.c | 2

[PATCH] libbb: reduce the overhead of single parameter bb_error_msg() calls

: -938 bytes Regards, James Byrne 0001-libbb-reduce-the-overhead-of-single-parameter-bb_err.patch.gz Description: application/gzip ___ busybox mailing list busybox@busybox.net http://lists.busybox.net/mailman/listinfo/busybox

Re: [PATCH] config: PID_FILE_PATH required for FEATURE_CROND_SPECIAL_TIMES

On 17/07/2019 16:53, James Byrne wrote: When crond is built with FEATURE_CROND_SPECIAL_TIMES enabled, it creates a file called 'crond.reboot' at CONFIG_PID_FILE_PATH, but if FEATURE_PIDFILE is disabled, this will be an empty string and the file will be created in the root directory, which

Re: [PATCH] config: PID_FILE_PATH required for FEATURE_CROND_SPECIAL_TIMES

Hi, On 27/08/2019 19:50, Markus Gothe wrote: Having a quick look, I'd say it introduces an unexpected behaviour at best. I'm afraid I don't quite understand your objection. I don't see how this introduces unexpected behaviour, it's trying to remove the unexpected behaviour that you

[PATCH] config: PID_FILE_PATH required for FEATURE_CROND_SPECIAL_TIMES

depend on FEATURE_CROND_SPECIAL_TIMES as well as FEATURE_PIDFILE so that you get sensible behaviour in crond when FEATURE_PIDFILE is switched off. Signed-off-by: James Byrne --- Config.in | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/Config.in b/Config.in index

Re: [PATCH] config: PID_FILE_PATH required for FEATURE_CROND_SPECIAL_TIMES

On 27/08/2019 14:51, James Byrne wrote: On 17/07/2019 16:53, James Byrne wrote: When crond is built with FEATURE_CROND_SPECIAL_TIMES enabled, it creates a file called 'crond.reboot' at CONFIG_PID_FILE_PATH, but if FEATURE_PIDFILE is disabled, this will be an empty string and the file