[RFC] global/clang-format: Add .clang-format configuration for consistent formatting#74
Open
softworkz wants to merge 1 commit into
Open
[RFC] global/clang-format: Add .clang-format configuration for consistent formatting#74softworkz wants to merge 1 commit into
softworkz wants to merge 1 commit into
Conversation
softworkz
changed the title
…tent formatting This is an attempt to create and establish a common definition for code formatting. Besides .clang-format, there don't seem to be many good candidates for C when looking for non-proprietary open-source solutions, so there's wasn't really much choice. I have tried to configure everything according to the current guidelines, to which it should come pretty close. There are a few things for which I couldn't find any FFmpeg rules, or where it wasn't clear and I made choices that seemed reasonable. This is in no way intended to prescribe any formatting detail rules, it's rather meant as an invitation to collaborate on this and ideally end up with something "official" that allows to check and fix formatting in CI flows or Patchwork and locally for everybody using editors with clang-format support or using clang-format from the command line. Signed-off-by: softworkz <softworkz@hotmail.com>
softworkz
force-pushed
the
submit_clang_format
branch
from
9d4e79d to
272c74b
Compare
Collaborator
Author
|
/submit |
|
Submitted as pull.74.ffstaging.FFmpeg.1745279559776.ffmpegagent@gmail.com To fetch this version into To fetch this version to local tag |
|
On the FFmpeg mailing list, "softworkz ." wrote (reply to this): |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This is an attempt to create and establish a common definition for
code formatting. Besides .clang-format, there don't seem to be many
good candidates for C when looking for non-proprietary open-source
solutions, so there's wasn't really much choice.
I have tried to configure everything according to the current
guidelines, to which it should come pretty close. There are a few
things for which I couldn't find any FFmpeg rules, or where it wasn't
clear and I made choices that seemed reasonable.
This is in no way intended to prescribe any formatting detail rules,
it's rather meant as an invitation to collaborate on this and ideally
end up with something "official" that allows to check and fix
formatting in CI flows or Patchwork and locally for everybody using
editors with clang-format support or using clang-format from the
command line.
Signed-off-by: softworkz softworkz@hotmail.com