From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
Cc: "Howlett, Liam \(Wind River\)" <liam.howlett@windriver.com>,
"bitbake-devel@lists.openembedded.org"
<bitbake-devel@lists.openembedded.org>,
Gary Thomas <gary@mlbassoc.com>
Subject: Re: [PATCH v3] fetch2: Add BB_ALLOWED_NETWORKS support
Date: Tue, 16 Jun 2015 09:40:15 +0100 [thread overview]
Message-ID: <1946263.B0TEDLLAIC@peggleto-mobl.ger.corp.intel.com> (raw)
In-Reply-To: <1FDE9321-AA20-49D9-A4BE-A4B4514439DB@gmail.com>
On Monday 15 June 2015 23:47:29 Bernhard Reutner-Fischer wrote:
> On June 15, 2015 4:03:11 PM GMT+02:00, "Rifenbark, Scott M"
<scott.m.rifenbark@intel.com> wrote:
> >Hi,
> >
> >Here is a first draft of documenting the BB_ALLOWED_NETWORKS variable
> >in the BitBake User Manual. I re-wrote the original text to be active
> >voice and applied some different organization of the facts to help the
> >flow out. Regarding Gary's input about BB_NO_NETWORK..... I took a
> >half guess at incorporating it. Please look this new description over
> >and let me know of any corrections I need to make.
> >http://www.yoctoproject.org/docs/1.9/bitbake-user-manual/bitbake-user-manua
> >l.html#var-BB_ALLOWED_NETWORKS.
> Was the v3 fixed / extended to allow for netmasks, btw?
> Think
> /etc/hosts
> foo.example.com 10.0.0.1
> bar.example.com 10.0.0.254
> baz.example.com ::1
>
> BB_ALLOWED_NETWORKS = 10.0.0.0/24 1.1.1.1/31 ::1/127
I don't believe so. You can see what actually went in here:
http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=59ce7d02a57e0a642d839ab48677f6ac1886180f
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2015-06-16 8:40 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-31 18:39 [PATCH] fetch2: Add BB_TRUSTED_NETWORK support Liam R. Howlett
2015-03-31 18:39 ` Liam R. Howlett
2015-04-15 18:17 ` [PATCH v2] " Liam R. Howlett
2015-04-15 18:17 ` Liam R. Howlett
2015-04-16 17:06 ` [PATCH v3] fetch2: Add BB_ALLOWED_NETWORKS support Liam R. Howlett
2015-04-16 17:23 ` Liam R. Howlett
2015-05-12 11:17 ` Richard Purdie
2015-05-12 14:28 ` Liam R. Howlett
2015-06-15 13:28 ` Paul Eggleton
2015-06-15 13:30 ` Rifenbark, Scott M
2015-06-15 13:38 ` Gary Thomas
2015-06-15 14:03 ` Rifenbark, Scott M
2015-06-15 21:47 ` Bernhard Reutner-Fischer
2015-06-16 8:40 ` Paul Eggleton [this message]
2015-06-16 13:42 ` Liam R. Howlett
2015-06-16 15:25 ` Rifenbark, Scott M
2015-06-16 19:24 ` Liam R. Howlett
2015-06-16 19:25 ` Rifenbark, Scott M
2015-06-16 22:16 ` Rifenbark, Scott M
2015-04-15 19:37 ` [PATCH] fetch2: Add BB_TRUSTED_NETWORK support Christopher Larson
2015-04-15 19:42 ` Bernhard Reutner-Fischer
2015-04-16 14:16 ` Liam R. Howlett
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=1946263.B0TEDLLAIC@peggleto-mobl.ger.corp.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=gary@mlbassoc.com \
--cc=liam.howlett@windriver.com \
--cc=rep.dot.nop@gmail.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.