From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [1.30][PATCH 0/1] Backport fetch environment fix to 1.30
Date: Wed, 25 May 2016 10:20:36 +1200 [thread overview]
Message-ID: <cover.1464128340.git.paul.eggleton@linux.intel.com> (raw)
This will allow variables such as GIT_SSL_CAINFO through from the
external environment to the fetch environment, which in OE will allow
buildtools-tarball's included git version to find the included
ca-certificates data.
The following changes since commit 9ea7d3ec59c2b09ae60cf0c7f18472355bfb98d7:
toaster: fix progress bar in MySQL environment (2016-05-13 17:45:31 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib paule/bb-git-ssl-cainfo-1.30
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=paule/bb-git-ssl-cainfo-1.30
Ross Burton (1):
fetch2: export DBUS_SESSION_BUS_ADDRESS to support authentication
agents
lib/bb/fetch2/__init__.py | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
--
2.5.5
next reply other threads:[~2016-05-24 22:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-24 22:20 Paul Eggleton [this message]
2016-05-24 22:20 ` [1.30][PATCH 1/1] fetch2: export DBUS_SESSION_BUS_ADDRESS to support authentication agents Paul Eggleton
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=cover.1464128340.git.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox