From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1 of 2] infra: permissions/users/device tables: avoid adding empty entries
Date: Wed, 28 May 2014 22:04:06 +0200 [thread overview]
Message-ID: <87fvjtbrgp.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <f9a9da19bf34a6862ec5.1400762140@argentina> (Thomas De Schampheleire's message of "Thu, 22 May 2014 14:35:40 +0200")
>>>>> "Thomas" == Thomas De Schampheleire <patrickdepinguin@gmail.com> writes:
> In pkg-generic.mk, an entry would be added to each of the permissions,
> devices and users tables, even if FOO_PERMISSIONS/DEVICES/USERS is empty. In
> that last case, the entry would contain only the separator, which is
> substituted to '\n' in fs/common.mk.
> For configurations with many packages, this would render the build output a
> bit odd, containing many \n instances (even though the end result in the
> target would of course be the same).
> This patch cleans up the build output by only adding to these tables when
> the package actually specified contents for them.
> Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
Committed, thanks.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2014-05-28 20:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 12:35 [Buildroot] [PATCH 0 of 2] Small cleanups of build output Thomas De Schampheleire
2014-05-22 12:35 ` [Buildroot] [PATCH 1 of 2] infra: permissions/users/device tables: avoid adding empty entries Thomas De Schampheleire
2014-05-22 22:30 ` Romain Naour
2014-05-28 20:04 ` Peter Korsgaard [this message]
2014-05-22 12:35 ` [Buildroot] [PATCH 2 of 2] fs/tar: use qstrip to clean up build output Thomas De Schampheleire
2014-05-22 22:30 ` Romain Naour
2014-05-28 20:04 ` Peter Korsgaard
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=87fvjtbrgp.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--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