From: Gyan Doshi <ffmpeg@gyani.pro> To: ffmpeg-devel@ffmpeg.org Subject: Re: [FFmpeg-devel] [PATCH v4] doc/developer: update outdated information Date: Sun, 2 Jun 2024 17:28:24 +0530 Message-ID: <d12f1aff-2a7f-4849-a874-fc37f3324314@gyani.pro> (raw) In-Reply-To: <20240602081202.96768-1-marcus@marcusspencer.xyz> On 2024-06-02 01:42 pm, Marcus B Spencer wrote: > Codec IDs have split from `avcodec.h` into `codec_id.h`. > > General documentation contents (which are now in > `general_contents.texi`) have split from the header in `general.texi`. > > Update the developer documentation to match these changes. Mention the commits in the msg. Else, LGTM. Regards, Gyan > > Signed-off-by: Marcus B Spencer <marcus@marcusspencer.xyz> > --- > doc/developer.texi | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/doc/developer.texi b/doc/developer.texi > index 63835dfa06..89e8bec60f 100644 > --- a/doc/developer.texi > +++ b/doc/developer.texi > @@ -682,7 +682,7 @@ number) in @file{libavcodec/version.h} or @file{libavformat/version.h}? > Did you register it in @file{allcodecs.c} or @file{allformats.c}? > > @item > -Did you add the AVCodecID to @file{avcodec.h}? > +Did you add the AVCodecID to @file{codec_id.h}? > When adding new codec IDs, also add an entry to the codec descriptor > list in @file{libavcodec/codec_desc.c}. > > @@ -697,7 +697,7 @@ already being compiled by some other rule, like a raw demuxer. > > @item > Did you add an entry to the table of supported formats or codecs in > -@file{doc/general.texi}? > +@file{doc/general_contents.texi}? > > @item > Did you add an entry in the Changelog? _______________________________________________ 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:[~2024-06-02 11:58 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-06-02 8:12 Marcus B Spencer 2024-06-02 11:58 ` Gyan Doshi [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=d12f1aff-2a7f-4849-a874-fc37f3324314@gyani.pro \ --to=ffmpeg@gyani.pro \ --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