From: Paul Sokolovsky <pmiscml@gmail.com>
To: "pHilipp Zabel" <philipp.zabel@gmail.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [oe-commits] org.oe.dev PDA-like machines with card slots: Enable "vfat" feature.
Date: Tue, 18 Dec 2007 13:35:00 +0200 [thread overview]
Message-ID: <978793792.20071218133500@gmail.com> (raw)
In-Reply-To: <74d0deb30712180217q5cb2c911l8a61567b5511b9d@mail.gmail.com>
Hello pHilipp,
Tuesday, December 18, 2007, 12:17:27 PM, you wrote:
> On Dec 18, 2007 3:47 AM, pfalcon commit
> <openembedded-commits@lists.openembedded.org> wrote:
>> PDA-like machines with card slots: Enable "vfat" feature.
>> * FAT-formatted cards are commodity, it's expectable them to be supported OOB.
> A machine feature "vfat" sounds strange. I think machine features
> should be about the hardware capabilities.
Yep, with this common sense in mind I quickly replied to Rod that
introducing it wouldn't help with "bloating" issue. Well, it instead
COMBINED feature.
> Unfortunately I don't have
> a proposal for a good name, but I'd prefer something like "cardslot"
> or some better generic term for SD/CF/MemoryStick/etc. capability.
> Then the distro can decide whether that means to add vfat support or
> ext2 or gnome-volume-manager or some fancy card formatting GUI app.
It's of course not about just name, but about feature processing
logic. Current COMBINED_FEATURES mechanism is at least very easy to
understand and provides great deal of detailed flexibility.
> regards
> Philipp
[]
--
Best regards,
Paul mailto:pmiscml@gmail.com
next prev parent reply other threads:[~2007-12-18 12:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1J4SUo-0006ZZ-Ov@linuxtogo.org>
2007-12-18 10:17 ` [oe-commits] org.oe.dev PDA-like machines with card slots: Enable "vfat" feature pHilipp Zabel
2007-12-18 11:35 ` Paul Sokolovsky [this message]
2007-12-18 14:38 ` pHilipp Zabel
2007-12-18 15:05 ` Paul Sokolovsky
2007-12-18 18:13 ` pHilipp Zabel
2007-12-18 19:22 ` Paul Sokolovsky
2007-12-18 21:07 ` Rod Whitby
2007-12-19 8:08 ` Koen Kooi
2007-12-19 9:14 ` Paul Sokolovsky
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=978793792.20071218133500@gmail.com \
--to=pmiscml@gmail.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=philipp.zabel@gmail.com \
/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.