From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludovic.courtes@inria.fr>
Cc: bavier@cray.com, 35666@debbugs.gnu.org,
pgarlick@tourbillion-technology.com
Subject: [bug#35666] [PATCH 0/2] Build a thread-safe hdf5 library
Date: Tue, 14 May 2019 14:02:41 +0200 [thread overview]
Message-ID: <87a7fp8cri.fsf@elephly.net> (raw)
In-Reply-To: <87d0kq1mr2.fsf@gnu.org>
Ludovic Courtès <ludovic.courtes@inria.fr> writes:
>> Do we have contact to the hdf5 developers to ask what the implications
>> of “enable-unsupported” are?
>
> I think it’s a warranty-void kind of flag: by passing it, the user
> asserts they understand they’re using a configuration not “officially
> supported” by the HDF Group, meaning that if it’s buggy, we’re on our
> own.
I don’t object to adding the option. It sounds like you confirmed that
it fixes serious problems in practise, so I think it’s a good idea to
enable it.
--
Ricardo
prev parent reply other threads:[~2019-05-14 12:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 9:56 [bug#35666] [PATCH 0/2] Build a thread-safe hdf5 library Ludovic Courtès
2019-05-10 10:05 ` [bug#35666] [PATCH 1/2] gnu: hdf5: Build a thread-safe library Ludovic Courtès
2019-05-10 10:05 ` [bug#35666] [PATCH 2/2] gnu: hdf5: Add dependency on Perl Ludovic Courtès
2019-05-10 11:52 ` [bug#35666] [PATCH 0/2] Build a thread-safe hdf5 library Ricardo Wurmus
2019-05-10 13:07 ` Ludovic Courtès
2019-05-10 15:09 ` Eric Bavier
2019-05-14 7:28 ` Ludovic Courtès
2019-05-14 14:40 ` Eric Bavier
2019-05-10 15:27 ` Paul Garlick
2019-05-14 10:21 ` bug#35666: " Ludovic Courtès
2019-05-14 12:02 ` Ricardo Wurmus [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=87a7fp8cri.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=35666@debbugs.gnu.org \
--cc=bavier@cray.com \
--cc=ludovic.courtes@inria.fr \
--cc=pgarlick@tourbillion-technology.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).