Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/news/news-v5.0.x.rst
Original file line number Diff line number Diff line change
Expand Up @@ -10,11 +10,11 @@ Open MPI version v5.0.1rc1

- Internal PMIx and PRRTe versions:

- PMIx (v4.2.8rc1-1-g0e09e062). Commit hash: ``0e09e062e8cefe0feb18ea37d768ded213053d68``.
- PRRTE (v3.0.3rc1-2-g33aa50909f). Commit hash: ``33aa50909fe2c223f9f515fae120cd6a21d04653``.
- PMIx (v4.2.8). Commit hash: ``d1c1ed0c2e64f19ad49291241a43630ea7fdce28``.
- PRRTE (v3.0.3). Commit hash: ``e383f5ad70c2633420d3425e9fb67e69b6bfd9c4``.

- Bugfixes and changes (in chronological order)

Comment on lines 11 to +17
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't worry about this. We will update the doc again.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For future releases, it would probably be good to automate this section of the doc (i.e., grab the specific git commits dynamically). It would be just a little less for a human to need to do, and probably be less error-prone.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes... though I also wonder if it is really necessary to include the commit hash. The release tag should be enough.

- Various documentation related updates and changes
- Fix a bunch of compiler warnings
- Sessions: fix a problem with fortran MPI_Session_get_nth_pset interface
Expand Down