From: Carsten Schlote <carsten.schlote@gmail.com>
To: ptxdist@pengutronix.de
Cc: Carsten Schlote <schlote@vahanus.net>
Subject: [ptxdist] [PATCH 0/2] Updates for OSELAS.Toolchain
Date: Wed, 19 Aug 2020 12:10:51 +0200 [thread overview]
Message-ID: <20200819101053.2242864-1-schlote@vahanus.net> (raw)
- Updated MPFR lib to 4.1.0.
- Added additional download URL because of excessive timeouts with
existing urls.
Carsten Schlote (2):
host-mpfr: version bump 4.0.2 -> 4.1.0
host-mpfr: Add additional download source URL
rules/host-mpfr.make | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
--
2.25.1
_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de
To unsubscribe, send a mail with subject "unsubscribe" to ptxdist-request@pengutronix.de
next reply other threads:[~2020-08-19 10:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-19 10:10 Carsten Schlote [this message]
2020-08-19 10:10 ` [ptxdist] [PATCH 1/2] host-mpfr: version bump 4.0.2 -> 4.1.0 Carsten Schlote
2020-08-19 10:10 ` [ptxdist] [PATCH 2/2] host-mpfr: Add additional download source URL Carsten Schlote
2020-08-27 11:17 ` Ladislav Michl
2020-09-04 17:22 ` [ptxdist] [PATCH 0/2] Updates for OSELAS.Toolchain Michael Olbrich
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=20200819101053.2242864-1-schlote@vahanus.net \
--to=carsten.schlote@gmail.com \
--cc=ptxdist@pengutronix.de \
--cc=schlote@vahanus.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