From: "Ludovic Courtès" <ludo@gnu.org>
To: "Nicolò Balzarotti" <anothersms@gmail.com>
Cc: 35388-done@debbugs.gnu.org
Subject: bug#35388: [PATCH] gnu: julia: Update to 1.1.0
Date: Wed, 24 Jul 2019 00:40:52 +0200 [thread overview]
Message-ID: <875znsz85n.fsf@gnu.org> (raw)
In-Reply-To: <CAO7Ox=a2q__mYrKWmHo5kgoZ1Fvtr8xbU67N7Y__kNnbFAKogg@mail.gmail.com> ("Nicolò Balzarotti"'s message of "Sun, 21 Jul 2019 10:43:01 +0000")
Hi Nicolò!
Nicolò Balzarotti <anothersms@gmail.com> skribis:
> After the longest week ever, I'm back. I had to power off my build server
> because is a bit noisy, and building llvm on a laptop is slow.
Heheh. :-)
> From 76e37b96a5670a0653187e7512eef8776902276c Mon Sep 17 00:00:00 2001
> From: =?UTF-8?q?Nicol=C3=B2=20Balzarotti?= <nicolo@nixo.xyz>
> Date: Sun, 21 Jul 2019 11:18:45 +0200
> Subject: [PATCH] gnu: julia: Update to 1.1.1
> To: guix35388@debbugs.gnu.org
> Cc: Nicolò Balzarotti <anothersms@gmail.com>
>
> ---
> gnu/packages/julia.scm | 335 ++++++++++++++++++++++++++---------------
> 1 file changed, 211 insertions(+), 124 deletions(-)
Pushed as 7304d5623ab5cc35289cb1535cbd0d8a37691fac! \o/
I changed a few things to your patch to minimize changes (whitespace
changes, etc.), to avoid tabs, and to build only two LLVM backends. I
also added a commit log that follows our conventions.
Please take a look and let me know if anything is amiss!
Anyway, it took a loooong time but it successfully built for me on
x86_64-linux. Thank you!
Ludo’.
prev parent reply other threads:[~2019-07-23 22:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0190423085235.21419-1-anothersms@gmail.com>
2019-04-25 7:51 ` [bug#35388] [PATCH] gnu: julia: Update to 1.1.0 Nicolò Balzarotti
2019-05-06 8:43 ` Ludovic Courtès
2019-05-27 14:26 ` Ludovic Courtès
2019-05-27 20:06 ` Nicolò Balzarotti
2019-07-21 10:43 ` Nicolò Balzarotti
2019-07-23 22:40 ` Ludovic Courtès [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875znsz85n.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=35388-done@debbugs.gnu.org \
--cc=anothersms@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).