From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/bird: add a unprivileged user
Date: Sun, 23 Jun 2019 18:10:55 +0200 [thread overview]
Message-ID: <20190623181055.518d5d0f@windsurf> (raw)
In-Reply-To: <20190318110547.177223b9@windsurf>
On Mon, 18 Mar 2019 11:05:47 +0100
Thomas Petazzoni <thomas.petazzoni@bootlin.com> wrote:
> > If your prefer to wait, I'll resubmit a patch with the start-stop-daemon
> > script later.
>
> Yes, indeed, I think it makes more sense to have the new user created
> together with an init script that actually uses it.
Unless I missed it, we didn't receive a new patch that adds the init
script for bird. I'm now going to mark the "package/bird: add a
unprivileged user" patch as "Changes Requested" in patchwork. So if you
don't resubmit a new patch, we will forget about this topic.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-06-23 16:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 10:56 [Buildroot] [PATCH 1/1] package/bird: add a unprivileged user Adrien Gallouët
2019-03-17 16:49 ` Thomas Petazzoni
2019-03-17 19:56 ` Adrien Gallouët
2019-03-18 10:05 ` Thomas Petazzoni
2019-06-23 16:10 ` Thomas Petazzoni [this message]
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=20190623181055.518d5d0f@windsurf \
--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