From: Gary Thomas <gary@mlbassoc.com>
To: Joshua Lock <josh@openedhand.com>
Cc: poky@yoctoproject.org
Subject: Re: README.hardware
Date: Thu, 09 Dec 2010 12:18:00 -0700 [thread overview]
Message-ID: <4D012B68.1000201@mlbassoc.com> (raw)
In-Reply-To: <1291921712.6078.48.camel@scimitar>
On 12/09/2010 12:08 PM, Joshua Lock wrote:
> On Wed, 2010-12-08 at 06:47 -0700, Gary Thomas wrote:
>> This file seems quite out of date, in fact it's not been updated
>> for 9 months :-(
>>
>> I don't know enough details to suggest a patch, but I think it
>> would be useful to update it to reflect "today's Poky/Yocto" world,
>> especially with the new visibility of the project.
>>
>
> I agree, although I'm also wondering if it would be better to have this
> information on the wiki where it can be more easily maintained by the
> community.
>
> Or a balance? any machine in meta/conf/machine documented in
> README.hardware and anything else on the wiki.
>
Wikis are great, but I tend to think of the Poky "checkout" tree
as self-sufficient. It has the full manual, etc, already so forcing
the user to have to go to the Wiki for such information (which is
really only overview anyway) would not be ideal. A combination
of hard files and Wiki would be OK as long as the README.hardware
at least mentions the "well sanctioned" ports, which right now
it does not.
I also tend to err on the side of my [sadly] many customers
that may have to work in non-internet-connected environments,
so making them have to get to a Wiki to find such answers is
not really acceptable.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2010-12-09 19:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-08 13:47 README.hardware Gary Thomas
2010-12-09 19:08 ` README.hardware Joshua Lock
2010-12-09 19:18 ` Gary Thomas [this message]
2010-12-09 19:35 ` README.hardware Tom Zanussi
2010-12-10 11:42 ` README.hardware Joshua Lock
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=4D012B68.1000201@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=josh@openedhand.com \
--cc=poky@yoctoproject.org \
/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