Prep for release v0.12: update dist, spec, and documentation #575
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gonsie
reviewed
Jun 3, 2024
| @@ -104,7 +104,7 @@ that each symbolic link refers to. | |||
| .B \-P, \-\-no\-dereference | |||
| Do not follow symbolic links in source paths. Effectviely allows | |||
| symbolic links to be copied when the link target is not valid | |||
| or there is not permission to read the link’s target. | |||
| or there is not permission to read the link\(aqs target. | |||
| @@ -125,7 +130,7 @@ Print the command usage, and the list of options available. | |||
| .SH EXPRESSIONS | |||
| .sp | |||
| An expression is made up of one or more conditions, where each condition specifies a field and a state. | |||
| A single condition consists of a field name, an ‘=’ sign, and a state name. | |||
| A single condition consists of a field name, an \(aq=\(aq sign, and a state name. | |||
| @@ -288,7 +293,7 @@ CONTENT=COMMON => EXISTS=COMMON@TYPE=COMMON@SIZE=COMMON@CONTENT=COMMON | |||
| .sp | |||
| A successful check on any other field also implies that EXIST=COMMON. | |||
| .sp | |||
| When used with the \-o option, one must also specify a file name at the end of the expression, separated with a ‘:’. | |||
| When used with the \-o option, one must also specify a file name at the end of the expression, separated with a \(aq:\(aq. | |||
|
Any traction on this? Thanks :) |
Update the dist, specfile used for rpm, and documentation to specify v0.12 for the release. Signed-off-by: Olaf Faaland <faaland1@llnl.gov>
man pages include updates to the version number as well as new features and changes related to external factors like github URLs for asset downloads. See the release notes for details. Signed-off-by: Olaf Faaland <faaland1@llnl.gov>
ofaaland
force-pushed
the
release-0.12
branch
from
1ae6250
to
8f23850
Compare
|
I rebased my release-0.12 branch to include the |
|
@carbonneau1 @gonsie I am thinking of holding off on this a couple of weeks so we can add more tests, and pull those tests in, to improve confidence that we didn't introduce a regression with the commits landed to main branch for this release. If you have thoughts they would be welcome. |
carbonneau1
approved these changes
Oct 23, 2024
daltonbohning
approved these changes
Oct 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update the dist, specfile used for rpm, and documentation to specify v0.12 for the release.