From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: "Rifenbark, Scott M" <scott.m.rifenbark@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
"Robert P. J. Day" <rpjday@crashcourse.ca>
Subject: Re: FW: FW: how the &^$%^%@%^#$ does "file://defconfig" work?
Date: Mon, 13 May 2013 08:48:46 -0400 [thread overview]
Message-ID: <5190E12E.90205@windriver.com> (raw)
In-Reply-To: <41DEA4B02DBDEF40A0F3B6D0DDB123797FF35DAC@fmsmsx152.amr.corp.intel.com>
On 13-05-13 06:39 AM, Rifenbark, Scott M wrote:
> Touche Robert :) You made my day.
And mine!
Bruce
>
> Scott
>
>> -----Original Message-----
>> From: Robert P. J. Day [mailto:rpjday@crashcourse.ca]
>> Sent: Monday, May 13, 2013 2:01 AM
>> To: Rifenbark, Scott M
>> Cc: yocto@yoctoproject.org; Ashfield, Bruce
>> Subject: Re: FW: FW: [yocto] how the &^$%^%@%^#$ does "file://defconfig"
>> work?
>>
>> On Mon, 13 May 2013, Rifenbark, Scott M wrote:
>>
>>>> Bruce,
>>>>
>>>> Thanks for the very clear example and the analogy. I might add a
>> note
>>>> to the section that was confusing Robert. Sometimes he gets really
>>>> picky on what he reads...
>>
>> i resent that. and you could have used a comma after the word
>> "Sometimes" up there. :-)
>>
>> rday
>>
>> --
>>
>> ========================================================================
>> Robert P. J. Day Ottawa, Ontario, CANADA
>> http://crashcourse.ca
>>
>> Twitter: http://twitter.com/rpjday
>> LinkedIn: http://ca.linkedin.com/in/rpjday
>> ========================================================================
prev parent reply other threads:[~2013-05-13 12:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 6:41 FW: FW: how the &^$%^%@%^#$ does "file://defconfig" work? Rifenbark, Scott M
2013-05-13 9:00 ` Robert P. J. Day
2013-05-13 10:39 ` Rifenbark, Scott M
2013-05-13 12:48 ` Bruce Ashfield [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=5190E12E.90205@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=rpjday@crashcourse.ca \
--cc=scott.m.rifenbark@intel.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.