Peter Hill

Sorry @nbehrnd, to be clear, my issue is absolutely nothing to do with the compiler -- the code compiles fine, before and after running fprettify. It's purely about the warning...

Since #35 has been merged, all the GUI-related code is solely in `xdot.ui`, which should make unifying all the forks easier. Probably even more common code could be pulled out,...

I'm seeing this in https://github.com/boutproject/BOUT-dev, except that `github_changelog_generator` _can_ fetch closed PRs for the previous tag. That is, the latest tag is v4.3.2 and PRs merged since then aren't fetched,...

No worries. Yeah, it's a pain for sure. There are libraries that can handle building both static and shared, SUNDIALS for one. I'll have a look through their CMake again...

Support for the `mpi_f08` module is dependent on the combination of compiler and MPI implementation, but it does now seem to be available more often than not. If moving to...

Fair point -- I had assumed the `USE_MPI_F08` condition would be selected by the user to provide compatibility when they use `mpi_f08` themselves, but perhaps it might be best to...

Yes, we went through the exact same process and thinking! It's very annoying. At least it is possible to upload tarballs to previous releases, even if it is a bit...

@tclune Just to clarify, I'm pretty sure @kurtsansom 's issue above is unrelated to my recent changes, and is because the release tarball here: https://github.com/Goddard-Fortran-Ecosystem/pFUnit/releases/tag/v4.1.15 is not a git repo...

I'm pretty sure this error is because you've got quite an old version of git that requires `git submodule` commands to be run from the top-level directory. If you're on...

Fortran badly needs an equivalent to cppreference, including their [compiler support](https://en.cppreference.com/w/cpp/compiler_support) page. There's something similar on Fortranwiki, but it uses data from the Fortran Forum which is "does the latest...