From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] packages/Config.in: Alphabetical entries sorting
Date: Fri, 25 Oct 2013 11:58:01 +0200 [thread overview]
Message-ID: <526A40A9.3050800@mind.be> (raw)
In-Reply-To: <CAAXf6LU-7FuKBUeb+T8XdusNwma0B_Y6Vp8cbnCQk9oJ=An6PQ@mail.gmail.com>
On 25/10/13 10:48, Thomas De Schampheleire wrote:
> On Fri, Oct 25, 2013 at 10:32 AM, Maxime Hadjinlian
> <maxime.hadjinlian@gmail.com> wrote:
>> On Fri, Oct 25, 2013 at 8:22 AM, Thomas De Schampheleire
>
>>>>> By the way, I don't think that 'firmwares' is correct English, the
>>>>> '-ware' already is plural, so it should be 'Misc devices firmware' or
>>>>> maybe plain 'Firmware' (are there other firmware packages in buildroot
>>>>> that are not part of this menu?).
>>>> After a very quick search, it seems you are right about the 's' of firmware.
>>>> About the naming of the menu, we already are in Hardware menu, so
>>>> talking about "devices" may seem redundant, and the Misc is maybe too
>>>> cumbersome. Although, a simple "Firmware" would not be very friendly.
>>>> How about settling on "Firmware's Devices" ? Give or take the casing.
>>>
>>> Then this should be 'Device firmware'
>>> because "Firmware's Devices" means "The devices of firmware" which is
>>> not what you intend to say.
>>>
>>> I'm not convinced there exists firmware for something else than a
>>> device though. For me 'Firmware' or 'Device firmware' are both ok.
>> I just though "Firmware" to be a bit blunt, but I am not really good
>> at wordings as you may have seen so I am OK with whatever is wanted.
>
> I'm looking forward to the opinion of others. I am just one of the
> developers, like you.
Firmware blobs?
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
prev parent reply other threads:[~2013-10-25 9:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-24 13:16 [Buildroot] [PATCH 1/2] packages/Config.in: Alphabetical entries sorting Maxime Hadjinlian
2013-10-24 13:16 ` [Buildroot] [PATCH 2/2] packages/Config.in: Fix case on entries titles Maxime Hadjinlian
2013-10-24 13:26 ` Thomas De Schampheleire
2013-10-24 14:13 ` Maxime Hadjinlian
2013-10-24 13:36 ` [Buildroot] [PATCH 1/2] packages/Config.in: Alphabetical entries sorting Thomas De Schampheleire
2013-10-24 14:11 ` Maxime Hadjinlian
2013-10-25 6:22 ` Thomas De Schampheleire
2013-10-25 8:32 ` Maxime Hadjinlian
2013-10-25 8:48 ` Thomas De Schampheleire
2013-10-25 9:58 ` Arnout Vandecappelle [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=526A40A9.3050800@mind.be \
--to=arnout@mind.be \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.