From: krzysztof.taborski@nokia.com
To: openembedded-core@lists.openembedded.org
Subject: Re: Send bitbake cache (from recipe parsing) to another server
Date: Fri, 22 May 2020 05:13:38 -0700 [thread overview]
Message-ID: <21191.1590149618634672759@lists.openembedded.org> (raw)
In-Reply-To: <8e2dfbd8f03e3390dbeb3f02036c502b02b39169.camel@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 400 bytes --]
On Fri, May 22, 2020 at 05:04 AM, Richard Purdie wrote:
>
> Low. Its not designed to do that and you should never need to. Why
> can't it reparse?
I tried to reduce building time. I know, that it is not a big time, but multiplying by build count it could bring some benefits.
Nevertheless thanks for the answer. At least I know, that I should abandon this idea.
Br,
Krzysztof Taborski
[-- Attachment #2: Type: text/html, Size: 439 bytes --]
prev parent reply other threads:[~2020-05-22 12:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-22 11:59 Send bitbake cache (from recipe parsing) to another server krzysztof.taborski
2020-05-22 12:04 ` [OE-core] " Richard Purdie
2020-05-22 12:13 ` krzysztof.taborski [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=21191.1590149618634672759@lists.openembedded.org \
--to=krzysztof.taborski@nokia.com \
--cc=openembedded-core@lists.openembedded.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