From: Andrew Sayers <ffmpeg-devel@pileofstuff.org>
To: ffmpeg-devel@ffmpeg.org
Subject: [FFmpeg-devel] [PATCH 0/3] Fix /// comments that should be ///<
Date: Wed, 28 Feb 2024 17:09:38 +0000
Message-ID: <20240228171014.816489-1-ffmpeg-devel@pileofstuff.org> (raw)
This is the first in a planned series of patch series aimed at
fixing documentation issues, especially doxygen rendering.
I hope to post more as time allows in the coming days.
The first patch reflects the output of a `sed` command,
further patches fix edge cases not covered by `sed`.
Splitting commits this way allows merge conflicts
to be resolved by throwing the old commit away,
then running the command in the commit message.
Andrew Sayers (3):
all: Fix /// comments that should be ///<
avcodec/ivi: Make comments more Doxygen-friendly
avcodec/avcodec: Downgrade multi-member comment to non-Doxygen comment
libavcodec/avcodec.h | 10 +++++-----
libavcodec/bsf/noise.c | 24 ++++++++++++------------
libavcodec/ivi.h | 15 +++++++--------
libavfilter/vf_deshake.c | 2 +-
libavformat/rmdec.c | 4 ++--
5 files changed, 27 insertions(+), 28 deletions(-)
_______________________________________________
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".
next reply other threads:[~2024-02-28 17:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 17:09 Andrew Sayers [this message]
2024-02-28 17:09 ` [FFmpeg-devel] [PATCH 1/3] all: " Andrew Sayers
2024-02-28 17:09 ` [FFmpeg-devel] [PATCH 2/3] avcodec/ivi: Make comments more Doxygen-friendly Andrew Sayers
2024-02-28 17:09 ` [FFmpeg-devel] [PATCH 3/3] avcodec/avcodec: Downgrade multi-member comment to non-Doxygen comment Andrew Sayers
2024-03-04 16:42 ` [FFmpeg-devel] [PATCH 0/3] Fix /// comments that should be ///< Stefano Sabatini
2024-03-04 16:49 ` Andreas Rheinhardt
2024-03-04 17:00 ` Stefano Sabatini
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=20240228171014.816489-1-ffmpeg-devel@pileofstuff.org \
--to=ffmpeg-devel@pileofstuff.org \
--cc=ffmpeg-devel@ffmpeg.org \
/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