Skip to content

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
(cherry picked from commit 2a0f095)

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>
(cherry picked from commit 2a0f095)
@gpaulsen gpaulsen requested a review from jsquyres April 14, 2021 20:14
@jsquyres jsquyres changed the title Fixing .clang-format to allow it to work with v10 v5.0: Fixing .clang-format to allow it to work with v10 Apr 14, 2021
@jsquyres jsquyres added this to the v5.0.0 milestone Apr 14, 2021
@gpaulsen gpaulsen merged commit cc0951b into open-mpi:v5.0.x Apr 15, 2021
@gpaulsen gpaulsen deleted the topic/v5.0.x/clang-format-v10 branch April 15, 2021 11:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants