From: Robert Yang <liezhi.yang@windriver.com>
To: "Rifenbark, Scott M" <scott.m.rifenbark@intel.com>,
"bitbake-devel@lists.openembedded.org"
<bitbake-devel@lists.openembedded.org>
Subject: Re: [PATCH 2/2] bitbake-user-manual-intro.xml: update for dump-signatures
Date: Mon, 7 Jul 2014 14:16:06 +0800 [thread overview]
Message-ID: <53BA3B26.4050407@windriver.com> (raw)
In-Reply-To: <41DEA4B02DBDEF40A0F3B6D0DDB1237983FB63A9@ORSMSX101.amr.corp.intel.com>
On 07/07/2014 02:13 PM, Rifenbark, Scott M wrote:
> Patch applied,
>
Sorry, this has not been approved, we need wait for RP's comments and update
it, and we should merge the part for bitbake first.
// Robert
> Thanks,
> Scott
>
>> -----Original Message-----
>> From: bitbake-devel-bounces@lists.openembedded.org [mailto:bitbake-
>> devel-bounces@lists.openembedded.org] On Behalf Of Robert Yang
>> Sent: Thursday, July 03, 2014 10:39 PM
>> To: bitbake-devel@lists.openembedded.org
>> Subject: [bitbake-devel] [PATCH 2/2] bitbake-user-manual-intro.xml: update
>> for dump-signatures
>>
>> Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
>> ---
>> .../bitbake-user-manual-intro.xml | 10 ++++++----
>> 1 file changed, 6 insertions(+), 4 deletions(-)
>>
>> diff --git a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.xml
>> b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.xml
>> index ae267b4..e4025a8 100644
>> --- a/bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.xml
>> +++ b/bitbake/doc/bitbake-user-manual/bitbake-user-manual-intro.xml
>> @@ -471,11 +471,13 @@
>> -D, --debug Increase the debug level. You can specify this more
>> than once.
>> -n, --dry-run Don't execute, just go through the motions.
>> - -S DUMP_SIGNATURES, --dump-signatures=DUMP_SIGNATURES
>> + -S SIGNATURE_HANDLER, --dump-signatures=SIGNATURE_HANDLER
>> Dump out the signature construction information, with
>> - no task execution. Parameters are passed to the
>> - signature handling code, use 'none' if no specific
>> - handler is required.
>> + no task execution. The SIGNATURE_HANDLER can be none
>> + or printdiff, while none means only dump the
>> + signature, printdiff means compare the dumped
>> + signature with the cached one.
>> +
>> -p, --parse-only Quit after parsing the BB recipes.
>> -s, --show-versions Show current and preferred versions of all recipes.
>> -e, --environment Show the global or per-package environment
>> complete
>> --
>> 1.7.9.5
>>
>> --
>> _______________________________________________
>> bitbake-devel mailing list
>> bitbake-devel@lists.openembedded.org
>> http://lists.openembedded.org/mailman/listinfo/bitbake-devel
>
>
next prev parent reply other threads:[~2014-07-07 6:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-04 5:38 [PATCH 0/2] bitbake: update help message for dump-signatures Robert Yang
2014-07-04 5:39 ` Robert Yang
2014-07-04 5:38 ` [PATCH 1/2] " Robert Yang
2014-07-04 5:39 ` Robert Yang
2014-07-04 7:36 ` Richard Purdie
2014-07-04 8:23 ` Robert Yang
2014-07-04 5:38 ` [PATCH 2/2] bitbake-user-manual-intro.xml: update " Robert Yang
2014-07-04 5:39 ` Robert Yang
2014-07-07 6:13 ` Rifenbark, Scott M
2014-07-07 6:16 ` Robert Yang [this message]
2014-07-07 6:18 ` Rifenbark, Scott M
2014-07-21 18:18 ` Richard Purdie
2014-07-22 6:50 ` Rifenbark, Scott M
2014-07-22 8:12 ` Robert Yang
2014-07-22 8:35 ` Richard Purdie
2014-07-04 5:40 ` [PATCH 0/2] bitbake: update help message " Robert Yang
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=53BA3B26.4050407@windriver.com \
--to=liezhi.yang@windriver.com \
--cc=bitbake-devel@lists.openembedded.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 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.