From: zimoun <zimon.toutoune@gmail.com>
To: Jonathan Brielmaier <jonathan.brielmaier@web.de>,
Christopher Baines <mail@cbaines.net>,
44208@debbugs.gnu.org
Subject: [bug#44208] [PATCH 1/3] gnu: netcdf: Update to 4.7.4.
Date: Mon, 26 Oct 2020 13:46:32 +0100 [thread overview]
Message-ID: <86eell5f4n.fsf@gmail.com> (raw)
In-Reply-To: <dba47c43-a840-e705-dd0e-320c16651729@web.de>
Hi,
On Sun, 25 Oct 2020 at 21:26, Jonathan Brielmaier <jonathan.brielmaier@web.de> wrote:
> On 25.10.20 11:35, Christopher Baines wrote:
>> * gnu/packages/maths.scm (netcdf): Update to 4.7.4.
>> [source]: Remove the netcdf-tst_h_par.patch.
>> [inputs]: Update hdf5 and add curl.
>> * gnu/packages/patches/netcdf-tst_h_par.patch: Delete.
>> * gnu/local.mk (dist_patch_DATA): Remove deleted patch.
> Do we usually mention such changes in the commit message?
Why not? For example, recently I dug in Julia history and these would
have saved some time (read “git log” and not the diff themselves).
Well, my poor opinion. :-)
All the best,
simon
next prev parent reply other threads:[~2020-10-26 12:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-25 10:27 [bug#44208] [PATCH 0/3] Update netcdf Christopher Baines
2020-10-25 10:35 ` [bug#44208] [PATCH 1/3] gnu: netcdf: Update to 4.7.4 Christopher Baines
2020-10-25 10:35 ` [bug#44208] [PATCH 2/3] gnu: netcdf-fortran: Update to 4.5.3 Christopher Baines
2020-10-25 10:35 ` [bug#44208] [PATCH 3/3] gnu: python2-netcdf4: Remove package Christopher Baines
2020-10-25 20:26 ` [bug#44208] [PATCH 1/3] gnu: netcdf: Update to 4.7.4 Jonathan Brielmaier
2020-10-26 12:46 ` zimoun [this message]
2020-10-26 16:04 ` Christopher Baines
2020-10-26 10:52 ` Ludovic Courtès
2020-10-26 16:06 ` bug#44208: " Christopher Baines
2020-10-28 9:47 ` [bug#44208] " Ludovic Courtès
2020-10-31 16:12 ` Christopher Baines
2020-11-02 15:38 ` Ludovic Courtès
2020-11-02 23:43 ` Christopher Baines
2020-10-25 20:28 ` [bug#44208] [PATCH 0/3] Update netcdf Jonathan Brielmaier
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=86eell5f4n.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=44208@debbugs.gnu.org \
--cc=jonathan.brielmaier@web.de \
--cc=mail@cbaines.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.
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).