All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] busybox: don't remove S01logging when CONFIG_SYSLOGD is disabled
Date: Tue, 16 Jan 2018 20:38:58 +0100	[thread overview]
Message-ID: <87a7xdfval.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20180110220628.309B9835A1@busybox.osuosl.org> (Thomas Petazzoni's message of "Wed, 10 Jan 2018 23:03:59 +0100")

>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:

 > commit: https://git.buildroot.net/buildroot/commit/?id=84e835ea9261b3e844f1a18489dd89253e3eb839
 > branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master

 > The current busybox.mk explicitly removes S01logging if CONFIG_SYSLOGD
 > is disabled in the Busybox configuration. However:

 >  - This causes the removal of the S01logging script potentially
 >    installed by another package (currently syslog-ng, rsyslog and
 >    sysklogd can all install a S01logging script).

 >  - We generally don't try to clean-up stuff that we may have installed
 >    in a previous make invocation and that is no longer needed
 >    following a configuration change.

 > Fixes bug #10176

 > Reported-by: Karl Krach <mail@kkrach.de>
 > Fix-provided-by: Karl Krach <mail@kkrach.de>
 > Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>

Committed to 2017.11.x, thanks.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2018-01-16 19:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-10 22:03 [Buildroot] [git commit] busybox: don't remove S01logging when CONFIG_SYSLOGD is disabled Thomas Petazzoni
2018-01-16 19:38 ` Peter Korsgaard [this message]
2018-01-30 12:33 ` Peter Korsgaard

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=87a7xdfval.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.