From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] mutt: bump to version 1.5.24
Date: Fri, 2 Oct 2015 14:23:25 -0300 [thread overview]
Message-ID: <560EBD8D.3090205@zacarias.com.ar> (raw)
In-Reply-To: <38121FAB319C3344930C920E7B5183136A3DBDD1@LEMAIL01.le.imgtec.org>
On 02/10/15 14:21, Vincent Olivert Riera wrote:
> Dear Gustavo Zacarias,
>
> Is there a problem with downloading from an ftp? I think is better to download the sources from the official site.
>
> Regards,
>
> Vincent.
Hi.
Corporate firewalls tend to block ftp more than https.
Bitbucket is listed in the mutt homepage, ftp is listed as primary, but
it's just as official (yeah, bad wording).
Regards.
next prev parent reply other threads:[~2015-10-02 17:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 17:11 [Buildroot] [PATCH] mutt: bump to version 1.5.24 Gustavo Zacarias
2015-10-02 17:21 ` Vincent Olivert Riera
2015-10-02 17:23 ` Gustavo Zacarias [this message]
2015-10-02 17:34 ` Vincent Olivert Riera
2015-10-02 19:50 ` Peter Korsgaard
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=560EBD8D.3090205@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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