Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/sysklogd: bump to version 2.1.2
Date: Thu, 13 Aug 2020 10:25:05 +0200	[thread overview]
Message-ID: <20200813102505.2120931f@windsurf.home> (raw)
In-Reply-To: <20200812160843.24064-1-andreas.hilse@googlemail.com>

Hello Andreas,

Thanks for the patch.

On Wed, 12 Aug 2020 18:08:43 +0200
Andreas Hilse <andreas.hilse@googlemail.com> wrote:

> - fixes: sysklogd 1.6 klogd with newer glibcs: kernel messages are logged to user facility

I'd like to understand how disruptive/important this issue is. I.e,
should we have this sysklogd version bump be considered as a bug fix?

> - sysklogd removed klogd, functionality has been moved to syslogd
> - now supports config fragments in /etc/syslog.d
> - disabled sysklogd logger to not interfere with other loggers

I think the license change should also be mentioned in the commit log,
but that can be added when applying.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2020-08-13  8:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-12 16:08 [Buildroot] [PATCH 1/1] package/sysklogd: bump to version 2.1.2 Andreas Hilse
2020-08-13  8:25 ` Thomas Petazzoni [this message]
2020-08-14  9:10   ` Andreas Hilse
2020-12-05 21:21 ` Thomas Petazzoni
2020-12-08 20:41   ` Andreas Hilse
2020-12-09  8:11     ` Thomas Petazzoni
2020-12-29 15:03     ` Andreas Hilse
2020-12-29 15:13       ` Thomas Petazzoni
2020-12-29 18:11 ` [Buildroot] [PATCH v2 " Andreas Hilse
2021-01-16 19:33   ` Joachim Wiberg
2021-01-19 21:26     ` Thomas Petazzoni
2021-01-20 10:11       ` Andreas Hilse
2021-01-20 10:38         ` Thomas Petazzoni
2021-01-21 12:41       ` Joachim Wiberg
2021-01-19 21:22   ` Thomas Petazzoni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200813102505.2120931f@windsurf.home \
    --to=thomas.petazzoni@bootlin.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox