[PATCH] Bugfix: svlogd does not apply pattern match options when using timestamps

Svlogd reads an optional config file that can be used to select/deselect patterns when logging. This feature was not working when using the timestamping option as well (svlogd -tt LOGDIR). Svlogd was including the timestamp when trying to apply pattern matches. According to the svlogd docs, http://

Re: [PATCH 1/2] allow honouring libc provided SIGRTMIN/SIGRTMAX

On 2018-10-31 11:13, Denys Vlasenko wrote: > Applied, thanks! Thanks, but the commit message was mangled somehow, so now it just reads In any case, this is rather unfortunate: 36 34 I.e. the lines beginning with # were stripped, making it rather confusing. You may want to loo

Re: printf can't handle the '+' char in front of an integer

Hello, Just my two cents here. On Wed, Oct 31, 2018 at 12:34 PM Bernhard Reutner-Fischer wrote: > > > > > 64-bit double's mantissa is only 53 bits... > > > > With "long double" shenanigans, I managed to "improve" this to: > > > > $ ./busybox printf "%f\n" 18446744073709550592 1844674407370955366

Re: [PATCH] vi: remove duplicated code

Applied, thanks! On Tue, Apr 26, 2016 at 4:23 PM Ron Yorston wrote: > > At worst show_status_line() might be called needlessly when the > user presses ^L/^R, but I don't think we'll get many complaints > about that. > > function old new delta > do_

Re: printf can't handle the '+' char in front of an integer

On Wed, 31 Oct 2018 at 00:36, Denys Vlasenko wrote: > > On Fri, Oct 19, 2018 at 3:43 PM Bernhard Reutner-Fischer > wrote: > > On Fri, 19 Oct 2018 at 15:30, Bernhard Reutner-Fischer > > wrote: > > > On Fri, 19 Oct 2018 at 11:03, Cristian Ionescu-Idbohrn > > > wrote: > > > > Oh, an I should menti

Re: [PATCH 2/2] libbb/u_signal_names.c: don't check errno after bb_strtou

Applied, thanks! On Wed, Sep 12, 2018 at 5:39 PM Rasmus Villemoes wrote: > > Since we're comparing the return value to a smallish integer anyway, we > might as well use that bb_strtou() returns UINT_MAX for malformed > input. Referencing errno is kinda bloaty on glibc. Seems to save ~34 or > ~45 b

Re: [PATCH 1/2] allow honouring libc provided SIGRTMIN/SIGRTMAX

Applied, thanks! On Wed, Sep 12, 2018 at 5:39 PM Rasmus Villemoes wrote: > > When an application documents that it responds such and such to > SIGRTMIN+n, that almost always means with respect to the libc-provided > SIGRTMIN. Hence I disagree with the "more correct" in commit > 7b276fc17594. In an

RE: [PATCH] Add bc (Last patch)

> From: busybox On Behalf Of Gavin Howard > Sent: Tuesday, October 30, 2018 12:30 AM > > On Mon, Oct 29, 2018 at 4:46 PM Denys Vlasenko > wrote: > > > > On Mon, Oct 29, 2018 at 4:55 PM Gavin Howard > > wrote: > > >... > > +if (!(v->v = malloc(esize * BC_VEC_START_CAP))) return > > BC_STAT