From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 3/3] conf/bitbake.conf: use --no-check-certificate to avoid errors when wgetting from https
Date: Wed, 11 May 2011 10:01:12 +0100 [thread overview]
Message-ID: <1305104472.30391.306.camel@rex> (raw)
In-Reply-To: <237ad27052ac01cead340513a7057d81e0c2fcfe.1305095232.git.raj.khem@gmail.com>
On Tue, 2011-05-10 at 23:30 -0700, Khem Raj wrote:
> From: Otavio Salvador <otavio@ossystems.com.br>
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
> meta/conf/bitbake.conf | 8 ++++----
> 1 files changed, 4 insertions(+), 4 deletions(-)
Merged to master, thanks.
Richard
prev parent reply other threads:[~2011-05-11 9:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-11 6:29 [PATCH 0/3] Do not depend on BBFILES to compute scm dirs Khem Raj
2011-05-11 6:29 ` [PATCH 1/3] metadata_scm.bbclass: Use COREBASE to grok for SCM operations Khem Raj
2011-05-11 6:29 ` [PATCH 2/3] meta/conf/layer.conf: Remove packages/*bb from BBFILES Khem Raj
2011-05-11 6:30 ` [PATCH 3/3] conf/bitbake.conf: use --no-check-certificate to avoid errors when wgetting from https Khem Raj
2011-05-11 6:42 ` Khem Raj
2011-05-11 9:01 ` Richard Purdie [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=1305104472.30391.306.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--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