Skip to content

Fixing .clang-format to allow it to work with v10 #8748

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 14, 2021

Conversation

gpaulsen
Copy link
Member

On RHEL 8.3, the version of clang-format that Redhat provides is:

clang-format --version
clang-format version 10.0.1 (Red Hat 10.0.1-1.module+el8.3.0+7459+90c24896)
git --version
git v2.27.0

I tried to fix up master PR #8747 (master version of 8723) with the command:
git clang-format -v HEAD~1 but ran into some issues with clang-format
v10.0.1 being able to parse the .clang-format file.

I did not spend much time trying to find viable alternatives, instead
I would just remove the offending line in the .clang-format file and
rince/repeat.

Are these options that we could do without, so that we could run
clang-format with both v10 and v11?

Signed-off-by: Geoffrey Paulsen gpaulsen@us.ibm.com

On RHEL 8.3, the version of clang-format that Redhat provides is:

> clang-format --version
clang-format version 10.0.1 (Red Hat 10.0.1-1.module+el8.3.0+7459+90c24896)
> git --version
git v2.27.0

I tried to fix up master PR open-mpi#8747 (master version of 8723) with the command:
`git clang-format -v HEAD~1` but ran into some issues with clang-format
v10.0.1 being able to parse the .clang-format file.

I did not spend much time trying to find viable alternatives, instead
I would just remove the offending line in the .clang-format file and
rince/repeat.

Are these options that we could do without, so that we could run
clang-format with both v10 and v11?

Signed-off-by: Geoffrey Paulsen <gpaulsen@us.ibm.com>
@gpaulsen gpaulsen requested a review from hjelmn March 31, 2021 22:39
@gpaulsen
Copy link
Member Author

gpaulsen commented Apr 6, 2021

Discussed briefly on the chat today, to ask people's opinions.
On one hand this is not intended to be run by ALL developers (generally) so requiring a slightly less convenient newer version is probably okay.
On the other hand, if these are parameters that are not terribly visible, we may not care.
If no discussion in the next week or so, I'll just close this Draft.

Copy link
Member

@hjelmn hjelmn left a comment

Choose a reason for hiding this comment

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

None of the changes look like they will be a problem. They are all at the default value so likely the behavior will not change with this.

@gpaulsen
Copy link
Member Author

Thanks @Helmn.

@gpaulsen gpaulsen marked this pull request as ready for review April 14, 2021 20:06
@gpaulsen gpaulsen merged commit 6d237e8 into open-mpi:master Apr 14, 2021
@gpaulsen gpaulsen deleted the topic/master/clang-format-v10 branch April 14, 2021 20:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants