From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] API documentation
Date: Wed, 24 Aug 2022 20:45:21 +0200
Message-ID: <20220824184521.GS2088045@pb2> (raw)
In-Reply-To: <109c94b3-fa82-89c4-fd89-a13f7197f69c@nativewaves.com>
[-- Attachment #1.1: Type: text/plain, Size: 1187 bytes --]
Hi
On Wed, Aug 24, 2022 at 03:15:45PM +0200, Michael Riedl wrote:
> Hi,
>
> I saw on the FFmpeg website that for some stable versions there is no
> API documentation. The latest stable documentation (for version 4.1) is
> four years old.
>
> We managed to build the API documentation for 5.1
> (https://ffmpeg-docs.tools.nativewaves.com/5.1/index.html) and other
> stable versions (https://ffmpeg-docs.tools.nativewaves.com/). We happily
> offer to host the documentation (updated regularly) free of charge.
> Maybe our page can be linked on FFmpeg's documentation page
> (https://ffmpeg.org/documentation.html) to complete it with respect to
> recent releases.
>
> Please let me know what you think.
Fixed the doxy documentation on ffmpeg.org.
For git master it was and is automatically generated but for releases it was
and is manual.
I forgot generating it after 4.1 it seems, it wasnt in my list of things to
do for release for some reason
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
While the State exists there can be no freedom; when there is freedom there
will be no State. -- Vladimir Lenin
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: 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:[~2022-08-24 18:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-24 13:15 Michael Riedl
2022-08-24 18:45 ` Michael Niedermayer [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=20220824184521.GS2088045@pb2 \
--to=michael@niedermayer.cc \
--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