From: david.weidenkopf@arthrex.com
To: bitbake-devel@lists.openembedded.org
Subject: Re: Git operations during parse
Date: Mon, 13 Sep 2021 16:08:06 -0700 [thread overview]
Message-ID: <25324.1631574486288023043@lists.openembedded.org> (raw)
In-Reply-To: <0c08eb02be04e948204db6200fbd3312f38ff1ab.camel@linuxfoundation.org>
[-- Attachment #1: Type: text/plain, Size: 249 bytes --]
Thanks! Are there particular variables that play a role in avoiding network operations during parse? Is it SRCREV? BB_NO_NETWORK doesn't seem right for our use case. We want the build to update from our repos during fetch, just not during parsing.
[-- Attachment #2: Type: text/html, Size: 255 bytes --]
prev parent reply other threads:[~2021-09-13 23:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-13 18:23 Git operations during parse david.weidenkopf
2021-09-13 21:51 ` [bitbake-devel] " Richard Purdie
2021-09-13 23:08 ` david.weidenkopf [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=25324.1631574486288023043@lists.openembedded.org \
--to=david.weidenkopf@arthrex.com \
--cc=bitbake-devel@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 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.