From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] New makedevs.c which can now handle users/groups created via FOO_USERS
Date: Mon, 8 Jun 2015 23:28:50 +0200 [thread overview]
Message-ID: <20150608232850.017e1915@free-electrons.com> (raw)
In-Reply-To: <CACiQJzwO=snzcFXDJY7-eJ==dd7tcGrkvBahksHTv7UmfO_ZLA@mail.gmail.com>
Jonathan,
On Mon, 8 Jun 2015 16:39:59 -0400, Jonathan Boivin wrote:
> This new version is useful when a package create new users via
> FOO_USERS and want to use the username newly created into
> FOO_PERMISSIONS.
>
> http://pastebin.com/UK5WDm7X
Thanks. However, this is not the proper way of doing a patch submission
to Buildroot. See
http://buildroot.org/downloads/manual/manual.html#submitting-patches
for details on how to do a proper patch submission.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-06-08 21:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 20:39 [Buildroot] New makedevs.c which can now handle users/groups created via FOO_USERS Jonathan Boivin
2015-06-08 21:28 ` Thomas Petazzoni [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-06-08 20:33 Jonathan Boivin
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=20150608232850.017e1915@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