From: non-Jedi <non-Jedi@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: julia: update to 1.6.0.
Date: Fri, 26 Mar 2021 16:25:53 +0100 [thread overview]
Message-ID: <20210326152553.UJsggEEPHi4K-f7PyyK65kLfdmEoFsIzWUckgxXz1Og@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29758@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 812 bytes --]
New comment by non-Jedi on void-packages repository
https://github.com/void-linux/void-packages/pull/29758#issuecomment-808307802
Comment:
> I remember earlier versions passed the bast majority of tests but some still failed. If the number of failures isn't dramatically increasing, we shouldn't worry too much.
Ya. It's no different than it has been. I included that blurb so that people unfamiliar with the history wouldn't be confused by the CI failures.
> For licenses, just list both separated by a comma, _e.g._, "MIT, GPL-3.0-or-later". Just double check the right GPL version restrictions and use the SPDX identifier.
Will do. By the looks of it, it will just be a list of basically every prominent free software license in existence: https://github.com/JuliaLang/julia/blob/master/LICENSE.md
next prev parent reply other threads:[~2021-03-26 15:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-25 21:27 [PR PATCH] " non-Jedi
2021-03-26 1:16 ` non-Jedi
2021-03-26 1:22 ` ahesford
2021-03-26 1:24 ` ahesford
2021-03-26 15:25 ` non-Jedi [this message]
2021-03-26 21:56 ` ahesford
2021-03-30 4:15 ` [PR REVIEW] " ahesford
2021-03-30 4:15 ` ahesford
2021-03-31 12:40 ` [PR PATCH] [Updated] " non-Jedi
2021-03-31 12:41 ` non-Jedi
2021-03-31 15:21 ` non-Jedi
2021-03-31 18:13 ` [PR PATCH] [Merged]: " ahesford
2021-03-31 19:35 ` ahesford
2021-03-31 22:43 ` non-Jedi
2021-04-01 21:27 ` non-Jedi
2021-04-02 16:20 ` non-Jedi
2021-04-02 16:22 ` non-Jedi
2021-04-02 18:15 ` ahesford
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=20210326152553.UJsggEEPHi4K-f7PyyK65kLfdmEoFsIzWUckgxXz1Og@z \
--to=non-jedi@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).