From: Joachim Wiberg <troglobit@gmail.com>
To: buildroot@buildroot.org
Cc: Joachim Wiberg <troglobit@gmail.com>, thomas.petazzoni@bootlin.com
Subject: [Buildroot] [PATCH next 0/3] package/inadyn: start script rework + repost
Date: Sun, 5 Dec 2021 11:29:03 +0100 [thread overview]
Message-ID: <20211205102907.2836980-1-troglobit@gmail.com> (raw)
Hi Thomas, all!
This patch set contains the rework of the inadyn start script. It is
now modeled closely on BusyBox S01syslogd, as requested.
I'm also including a repost of the .conf example update and the switch
to use the upstrem systemd unit file.
Best regards
/Joachim
Joachim Wiberg (3):
package/inadyn: replace local systemd unit file with upstream
package/inadyn: refactor start script
package/inadyn: update inadyn.conf example
package/inadyn/S70inadyn | 100 ++++++++++++++++++++++------------
package/inadyn/inadyn.conf | 25 +++++++--
package/inadyn/inadyn.mk | 2 +-
package/inadyn/inadyn.service | 10 ----
4 files changed, 86 insertions(+), 51 deletions(-)
mode change 100644 => 100755 package/inadyn/S70inadyn
delete mode 100644 package/inadyn/inadyn.service
--
2.25.1
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next reply other threads:[~2021-12-05 10:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-05 10:29 Joachim Wiberg [this message]
2021-12-05 10:29 ` [Buildroot] [PATCH next 1/3] package/inadyn: replace local systemd unit file with upstream Joachim Wiberg
2021-12-05 10:32 ` Joachim Wiberg
2021-12-05 10:29 ` [Buildroot] [PATCH next 2/3] package/inadyn: refactor start script Joachim Wiberg
2022-01-09 8:57 ` Peter Korsgaard
2021-12-05 10:29 ` [Buildroot] [PATCH next 3/3] package/inadyn: update inadyn.conf example Joachim Wiberg
2021-12-11 20:42 ` Arnout Vandecappelle
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=20211205102907.2836980-1-troglobit@gmail.com \
--to=troglobit@gmail.com \
--cc=buildroot@buildroot.org \
--cc=thomas.petazzoni@bootlin.com \
/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;
as well as URLs for NNTP newsgroup(s).