From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Changing permission recursively
Date: Fri, 13 Mar 2015 07:32:26 +0100 [thread overview]
Message-ID: <20150313073226.29f6bc55@free-electrons.com> (raw)
In-Reply-To: <5501F7C0.5050309@mind.be>
Dear Arnout Vandecappelle,
On Thu, 12 Mar 2015 21:32:00 +0100, Arnout Vandecappelle wrote:
> I think it would be easier to extend package/makedevs/makedevs.c to support
> recursive operation.
Yes, I agree. It seems quite usual to need an entire subtree with a
certain set of ownership/permissions.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-03-13 6:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-12 9:08 [Buildroot] Changing permission recursively Angelo Compagnucci
2015-03-12 12:41 ` Matthew Weber
2015-03-12 13:53 ` Angelo Compagnucci
2015-03-12 17:55 ` Baruch Siach
2015-03-12 20:32 ` Arnout Vandecappelle
2015-03-13 6:32 ` Thomas Petazzoni [this message]
2015-03-13 6:40 ` Angelo Compagnucci
2015-03-13 6:31 ` Thomas Petazzoni
2015-03-13 6:46 ` Angelo Compagnucci
2015-03-13 10:27 ` Baruch Siach
2015-03-13 10:53 ` Thomas Petazzoni
2015-03-13 10:59 ` Angelo Compagnucci
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=20150313073226.29f6bc55@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