From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] pppd: fix url
Date: Mon, 20 Apr 2015 23:25:18 +0200 [thread overview]
Message-ID: <20150420232518.7bf0f1b6@free-electrons.com> (raw)
In-Reply-To: <55356B4C.8030204@mind.be>
Dear Arnout Vandecappelle,
On Mon, 20 Apr 2015 23:10:36 +0200, Arnout Vandecappelle wrote:
> Actually, we prefer to avoid https because of potential issues with
> certificates and limitations of corporate firewalls. And the http version works.
But redirects to https://, so using https:// directly is basically the
same.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-04-20 21:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-20 17:47 [Buildroot] [git commit] pppd: fix url Thomas Petazzoni
2015-04-20 21:10 ` Arnout Vandecappelle
2015-04-20 21:25 ` Thomas Petazzoni [this message]
2015-04-20 21:26 ` Arnout Vandecappelle
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=20150420232518.7bf0f1b6@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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