Poky Project Discussions
 help / color / mirror / Atom feed
From: Saul Wold <saul.wold@intel.com>
To: "Rifenbark, Scott M" <scott.m.rifenbark@intel.com>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: [PATCH] fix a typo in usermanual on lazy default
Date: Thu, 02 Dec 2010 10:53:12 -0800	[thread overview]
Message-ID: <4CF7EB18.1000303@intel.com> (raw)
In-Reply-To: <DE8BA75F34A0404282AC5E15F691BC76910E@orsmsx504.amr.corp.intel.com>

On 11/22/2010 07:22 AM, Rifenbark, Scott M wrote:
> Where is this documentation?  (/Bitbake/doc/manual/usermanual.xml)
>
Scott, Qing

This would be a change that needs to be made to the upstream bitbake manual.

You could resend this patch to the  bitbake-dev@lists.berlios.de

Sau!



> -----Original Message-----
> From: Wold, Saul
> Sent: Friday, November 19, 2010 2:38 PM
> To: poky@yoctoproject.org; Rifenbark, Scott M
> Subject: Re: [poky] [PATCH] fix a typo in usermanual on lazy default
>
> On 11/18/2010 08:40 PM, Qing He wrote:
>> "??= ... is a lazy version of ??=", the second should be ?=
>>
>> Signed-off-by: Qing He<qing.he@intel.com>
>>
>
> Should all doc changes go through Scott R, and then into master that way?
>
> Just checking on process.
>
> Scott R: If you need help pulling changes let me know.
>
> Sau!
>
>> ---
>> diff --git a/bitbake/doc/manual/usermanual.xml b/bitbake/doc/manual/usermanual.xml
>> index 748ac31..2b7a0b5 100644
>> --- a/bitbake/doc/manual/usermanual.xml
>> +++ b/bitbake/doc/manual/usermanual.xml
>> @@ -97,7 +97,7 @@ share common metadata between many packages.</para></listitem>
>>                    <title>Setting a default value (??=)</title>
>>                    <para><screen><varname>A</varname>   ??= "somevalue"</screen></para>
>>                    <para><screen><varname>A</varname>   ??= "someothervalue"</screen></para>
>> -<para>If<varname>A</varname>   is set before the above, it will retain that value.  If<varname>A</varname>   is unset prior to the above,<varname>A</varname>   will be set to<literal>someothervalue</literal>.  This is a lazy version of ??=, in that the assignment does not occur until the end of the parsing process, so that the last, rather than the first, ??= assignment to a given variable will be used.</para>
>> +<para>If<varname>A</varname>   is set before the above, it will retain that value.  If<varname>A</varname>   is unset prior to the above,<varname>A</varname>   will be set to<literal>someothervalue</literal>.  This is a lazy version of ?=, in that the assignment does not occur until the end of the parsing process, so that the last, rather than the first, ??= assignment to a given variable will be used.</para>
>>                </section>
>>                <section>
>>                    <title>Immediate variable expansion (:=)</title>
>> _______________________________________________
>> poky mailing list
>> poky@yoctoproject.org
>> https://lists.yoctoproject.org/listinfo/poky
>>
>
>



      parent reply	other threads:[~2010-12-02 18:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-19  4:40 [PATCH] fix a typo in usermanual on lazy default Qing He
2010-11-19 22:38 ` Saul Wold
     [not found]   ` <DE8BA75F34A0404282AC5E15F691BC76910E@orsmsx504.amr.corp.intel.com>
2010-12-02 18:53     ` Saul Wold [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=4CF7EB18.1000303@intel.com \
    --to=saul.wold@intel.com \
    --cc=poky@yoctoproject.org \
    --cc=scott.m.rifenbark@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox