From: Stefano Sabatini <stefasab@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [IMPORTANT] Missing documentation
Date: Fri, 26 May 2023 07:48:15 +0200
Message-ID: <20230526054815.GA3241@mariano> (raw)
In-Reply-To: <CAPYw7P6pv5CzK+iEmuoiiXDNwhw7jxi-Ni5qjqn1WH5BaRwcxQ@mail.gmail.com>
On date Sunday 2023-05-21 11:45:35 +0200, Paul B Mahol wrote:
> On 5/20/23, Gyan Doshi <ffmpeg@gyani.pro> wrote:
> >
> > On 2023-05-20 05:20 pm, Paul B Mahol wrote:
> >> Hi,
> >>
> >> What is about muxer/demuxer documentation? More than half is not
> >> documented at all.
> >>
> >> I'm busy working on other things, what are doc maintainers doing?
> >
> > I was in the middle of doing this in the summer of 2021 when we went
> > into another lockdown and I got busy elsewhere.
> > Will resume this in some weeks.
>
> Thanks, maybe perhaps commit first the most popular formats
> muxers/demuxers that are currently not mentioned in .texi files
> especially ones that have options one can set/change.
Maybe it would be useful to start with a list of missing documentation
elements. We could either create a single trac issue or a single one
for each missing piece.
_______________________________________________
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 prev parent reply other threads:[~2023-05-26 5:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-20 11:50 Paul B Mahol
2023-05-20 13:58 ` Gyan Doshi
2023-05-21 9:45 ` Paul B Mahol
2023-05-26 5:48 ` Stefano Sabatini [this message]
2023-05-26 6:03 ` Gyan Doshi
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=20230526054815.GA3241@mariano \
--to=stefasab@gmail.com \
--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