From: "softworkz ." <softworkz-at-hotmail.com@ffmpeg.org>
To: softworkz <ffmpegagent@gmail.com>,
"ffmpeg-devel@ffmpeg.org" <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] [RFC] global/clang-format: Add .clang-format configuration for consistent formatting
Date: Mon, 21 Apr 2025 23:56:28 +0000
Message-ID: <BN0P223MB0358758A39DC074411914A68BAB82@BN0P223MB0358.NAMP223.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <pull.74.ffstaging.FFmpeg.1745279559776.ffmpegagent@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2980 bytes --]
> -----Original Message-----
> From: softworkz <ffmpegagent@gmail.com>
> Sent: Dienstag, 22. April 2025 01:53
> To: ffmpeg-devel@ffmpeg.org
> Cc: softworkz <softworkz@hotmail.com>; softworkz
> <softworkz@hotmail.com>
> Subject: [PATCH] [RFC] global/clang-format: Add .clang-format
> configuration for consistent formatting
>
> From: softworkz <softworkz@hotmail.com>
>
> 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>
> ---
> [RFC] global/clang-format: Add .clang-format configuration for
> consistent 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
>
> Published-As: https://github.com/ffstaging/FFmpeg/releases/tag/pr-
> ffstaging-74%2Fsoftworkz%2Fsubmit_clang_format-v1
> Fetch-It-Via: git fetch https://github.com/ffstaging/FFmpeg pr-
> ffstaging-74/softworkz/submit_clang_format-v1
> Pull-Request: https://github.com/ffstaging/FFmpeg/pull/74
>
> .clang-format | 81
> +++++++++++++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 81 insertions(+)
> create mode 100644 .clang-format
>
Here's the file as attachment.
[-- Attachment #2: .clang-format.zip --]
[-- Type: application/x-zip-compressed, Size: 1010 bytes --]
[-- Attachment #3: .clang-format.tar.gz --]
[-- Type: application/x-gzip, Size: 967 bytes --]
[-- Attachment #4: Type: text/plain, Size: 251 bytes --]
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
prev parent reply other threads:[~2025-04-21 23:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-21 23:52 softworkz
2025-04-21 23:56 ` softworkz . [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BN0P223MB0358758A39DC074411914A68BAB82@BN0P223MB0358.NAMP223.PROD.OUTLOOK.COM \
--to=softworkz-at-hotmail.com@ffmpeg.org \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=ffmpegagent@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git