From: Marius Bakke <mbakke@fastmail.com>
To: Thomas Danckaert <thomas.danckaert@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add python-netcdf4.
Date: Tue, 27 Dec 2016 16:59:05 +0100 [thread overview]
Message-ID: <8737h9xt12.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <20161227.101945.1947591597402188054.thomas.danckaert@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1185 bytes --]
Thomas Danckaert <thomas.danckaert@gmail.com> writes:
> From: Marius Bakke <mbakke@fastmail.com>
> Subject: Re: [PATCH] gnu: Add python-netcdf4.
> Date: Sat, 24 Dec 2016 14:59:35 +0100
>
>> Thomas Danckaert <thomas.danckaert@gmail.com> writes:
>>
>>> From b4b54b695e286c19332600c38d5e07fabee409f8 Mon Sep 17 00:00:00
>>> 2001
>>> From: Thomas Danckaert <thomas.danckaert@gmail.com>
>>> Date: Fri, 23 Dec 2016 15:06:43 +0100
>>> Subject: [PATCH] gnu: Add python-netcdf4.
>>>
>>> * gnu/packages/python.scm (python-netcdf4): New variable.
>>> ---
>>> gnu/packages/python.scm | 50
>>> +++++++++++++++++++++++++++++++++++++++++++++++++
>>> 1 file changed, 50 insertions(+)
>>
>> Thanks for this! The patch looks good, but the license seems to be
>> ISC
>> with parts covered by the expat license according to the COPYING
>> file.
>> Was there any particular reason you linked to the documentation?
>
> Hi,
>
> yes, you're right. I linked the documentation because the page
> included a license statement, but now I see the COPYING file in the
> repository is more accurate. So '(license:isc license:expat) it is.
Thanks for confirming, applied!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
prev parent reply other threads:[~2016-12-27 15:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-23 15:42 [PATCH] gnu: Add python-netcdf4 Thomas Danckaert
2016-12-24 13:59 ` Marius Bakke
2016-12-27 9:19 ` Thomas Danckaert
2016-12-27 15:59 ` Marius Bakke [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8737h9xt12.fsf@kirby.i-did-not-set--mail-host-address--so-tickle-me \
--to=mbakke@fastmail.com \
--cc=guix-devel@gnu.org \
--cc=thomas.danckaert@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.