All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: "Ourada, Paul" <Paul.Ourada@Covidien.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Yocto usability questions
Date: Fri, 18 Nov 2011 10:42:09 -0500	[thread overview]
Message-ID: <4EC67CD1.6080503@balister.org> (raw)
In-Reply-To: <4D9E0AFD9C2FCC428A8EAADA898F5B2D0E8A96@TAMANS-MB100V.thcg.net>

On 11/18/2011 10:02 AM, Ourada, Paul wrote:
> Jack said:
>> From: yocto-bounces@yoctoproject.org [mailto:yocto-bounces@yoctoproject.org] On Behalf Of Jack Mitchell
>> Sent: Friday, November 18, 2011 2:40 AM
>> To: yocto@yoctoproject.org
>> Subject: Re: [yocto] Yocto usability questions
>>
>> On 17/11/2011 21:38, Chris Tapp wrote: 
>> On 16 Nov 2011, at 22:07, Jeff Osier-Mixon wrote: 
>>
>>
>> Mark & everyone else listening: 
>>
>>
>> It is very frustrating when you come to an issue that isn't documented, however I have found the IRC an invaluable >resource as well as this mailing list. If documentation was to become more extensive I feel the categories should be >defined further and split into more documents.
> 
> I would just add that for some corporate/enterprise customers (such as myself), while IRC is great, it isn't as great an option because corporate IS locks down IRC protocols. To use IRC, I would have to do so from a non-work computer and likely outside of normal work hours, of which I already put in way more than my wife would prefer. :)

If I had a nickel for the .com guys ssh'ing into their home computers
(many times on non-standard ports) to run irc to get their work done,
I'd be retired :)

Philip

> 
> I really like Jack's list, though. I would like to pile on (again :)) that documentation, examples and explanation of terms are very important.
> 
> Paul
> 
> Paul E. Ourada
> Sr. Principal Software Engineer
> Covidien, Energy-based Devices
> 5920 Longbow Drive
> Boulder, CO 80301
> paul.ourada@covidien.com
> www.covidien.com
> Main: 303-530-2300
> Ofc: 303-581-6940
> Fax: 303-581-6741
> 
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto
> 


  reply	other threads:[~2011-11-18 15:42 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-16 22:07 Yocto usability questions Jeff Osier-Mixon
2011-11-16 23:39 ` Mark Hatle
2011-11-17  4:03   ` Ourada, Paul
2011-11-17  7:19 ` Koen Kooi
2011-11-17 13:06 ` Rainer Koenig
2011-11-17 14:25   ` Philip Balister
2011-11-17 21:38 ` Chris Tapp
2011-11-17 22:17   ` Brian Duffy
2011-11-17 23:19     ` Osier-mixon, Jeffrey
2011-11-18  9:40   ` Jack Mitchell
2011-11-18 15:02     ` Ourada, Paul
2011-11-18 15:42       ` Philip Balister [this message]
2011-11-18 15:56       ` Gary Thomas
2011-11-18 16:00         ` Philip Balister
2011-11-18 16:04           ` Gary Thomas
2011-11-18 16:56             ` Tom Rini
2011-11-18 16:56             ` Jack Mitchell
2011-11-18 17:20       ` Osier-mixon, Jeffrey
2011-11-18 19:40         ` Jeff Osier-Mixon
2011-11-18 20:12     ` Joshua Lock
2011-11-18 20:54       ` Tom Zanussi
2011-11-18 21:31         ` Osier-mixon, Jeffrey
2011-11-18 21:56           ` Chris Tapp
2011-11-18 22:32           ` Philip Balister
2011-11-18 22:36             ` Osier-mixon, Jeffrey
2011-11-22 12:52         ` Rainer Koenig
2011-11-22 15:23           ` Tom Zanussi
2011-11-22 16:49           ` Joshua Lock
2011-11-22 21:03             ` Chris Tapp
2011-11-22 22:52               ` Joshua Lock
  -- strict thread matches above, loose matches on Subject: below --
2018-12-21  5:16 Prasenjit Mahanti

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=4EC67CD1.6080503@balister.org \
    --to=philip@balister.org \
    --cc=Paul.Ourada@Covidien.com \
    --cc=yocto@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 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.