Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/4] scripts/mkusers: allow the creation of groups alone
Date: Wed, 22 Oct 2014 22:14:39 +0200	[thread overview]
Message-ID: <20141022221439.34ec2c5e@free-electrons.com> (raw)
In-Reply-To: <1413901599-27312-1-git-send-email-gustavo@zacarias.com.ar>

Dear Gustavo Zacarias,

On Tue, 21 Oct 2014 11:26:36 -0300, Gustavo Zacarias wrote:
> Let mkusers create groups alone, useful for supplementary permissions in
> udev/systemd for example where users can be added to later at runtime.
> Use a magic string "-" to signal that user creation should be skipped.
> 
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
> ---
>  support/scripts/mkusers | 2 ++
>  1 file changed, 2 insertions(+)

I've applied the four patches. On the documentation patch, I've taken
into account the suggestion of Yann to slightly adjust the commit.

Thanks a lot!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      parent reply	other threads:[~2014-10-22 20:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-21 14:26 [Buildroot] [PATCH 1/4] scripts/mkusers: allow the creation of groups alone Gustavo Zacarias
2014-10-21 14:26 ` [Buildroot] [PATCH 2/4] docs/manual: document makeusers group-only creation Gustavo Zacarias
2014-10-21 16:33   ` Yann E. MORIN
2014-10-21 14:26 ` [Buildroot] [PATCH 3/4] eudev: add input group Gustavo Zacarias
2014-10-21 16:33   ` Yann E. MORIN
2014-10-21 14:26 ` [Buildroot] [PATCH 4/4] systemd: " Gustavo Zacarias
2014-10-21 16:34   ` Yann E. MORIN
2014-10-21 16:30 ` [Buildroot] [PATCH 1/4] scripts/mkusers: allow the creation of groups alone Yann E. MORIN
2014-10-22 20:14 ` 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=20141022221439.34ec2c5e@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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