From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC] Unification of package comments on wchar, largefile, c++ support, thread, ... support
Date: Fri, 6 Sep 2013 14:28:07 +0200 [thread overview]
Message-ID: <20130906142807.44427db7@skate> (raw)
In-Reply-To: <CAAXf6LWyOHWDxPHkwga4mCy3UaCu93XEvAaXBpRz86wrQyPfnw@mail.gmail.com>
Dear Thomas De Schampheleire,
On Fri, 6 Sep 2013 12:37:05 +0200, Thomas De Schampheleire wrote:
> My question to the community: do we agree on the wording above (foo
> needs a toolchain w/ XXX, YYY)?
> If yes, then I will proceed to making the changes.
Do we really want to use all uppercase, even for things like thread
support?
We have the choice between:
(1) All lower-case
comment "directfb needs a toolchain w/ ipv6, rpc, thread, wchar"
(2) Lower-case, except when it doesn't make sense (acronyms)
comment "directfb needs a toolchain w/ IPv6, RPC, thread, wchar"
(3) All upper-case
comment "directfb needs a toolchain w/ IPv6, RPC, THREAD, WCHAR"
Also, the other question is which features do we mention. IPv6, RPC,
largefile, wchar, C++ and thread have always been there. However, the
need for dynamic library hasn't been always but in the comments, but
you were suggesting to include it. Also, what about MMU dependency ?
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-09-06 12:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-19 15:00 [Buildroot] [RFC] Unification of package comments on wchar, largefile, c++ support, thread, ... support Thomas De Schampheleire
2013-08-20 22:29 ` Arnout Vandecappelle
2013-08-21 5:28 ` Alexander Lukichev
2013-09-06 10:37 ` Thomas De Schampheleire
2013-09-06 12:28 ` Thomas Petazzoni [this message]
2013-09-06 14:34 ` Thomas De Schampheleire
2013-09-06 14:38 ` Michael Rommel
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=20130906142807.44427db7@skate \
--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