From: Marth64 <marth64@proxyid.net>
To: FFmpeg development discussions and patches
<ffmpeg-devel@ffmpeg.org>, Marth64 <marth64@proxyid.net>
Subject: Re: [FFmpeg-devel] [PATCH v2] doc/formats: clarify meaning of igndts as per definition in avformat.h
Date: Tue, 6 Feb 2024 17:59:38 -0600
Message-ID: <CA+28BfCFDDo70GEBGAGo8+sdJ+9JGE=uDajvELF6O6i-evSjYA@mail.gmail.com> (raw)
In-Reply-To: <ZcLHj+VbQ7A+skI7@mariano>
Glad to see this one fixed. Thank you!
On Tue, Feb 6, 2024 at 5:58 PM Stefano Sabatini <stefasab@gmail.com> wrote:
> On date Monday 2024-02-05 01:27:07 +0100, Stefano Sabatini wrote:
> > On date Sunday 2024-02-04 12:41:33 -0600, Marth64 wrote:
> > > This updates the documentation to be more clear about igndts,
> > > as per feedback in December variant of this patch (thank you)
> > >
> > > Signed-off-by: Marth64 <marth64@proxyid.net>
> > > ---
> > > doc/formats.texi | 3 ++-
> > > 1 file changed, 2 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/doc/formats.texi b/doc/formats.texi
> > > index 640b23b790..69fc1457a4 100644
> > > --- a/doc/formats.texi
> > > +++ b/doc/formats.texi
> > > @@ -46,7 +46,8 @@ Enable fast, but inaccurate seeks for some formats.
> > > @item genpts
> > > Generate missing PTS if DTS is present.
> > > @item igndts
> > > -Ignore DTS if PTS is set. Inert when nofillin is set.
> > > +Ignore DTS if PTS is also set. In case the PTS is set, the DTS value
> > > +is set to NOPTS. This is ignored when the @code{nofillin} flag is set.
> >
> > LGTM, I'll apply in a few days if I see no comments, thanks.
>
> Applied.
>
_______________________________________________
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-02-06 23:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-04 18:41 Marth64
2024-02-05 0:27 ` Stefano Sabatini
2024-02-06 23:58 ` Stefano Sabatini
2024-02-06 23:59 ` Marth64 [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='CA+28BfCFDDo70GEBGAGo8+sdJ+9JGE=uDajvELF6O6i-evSjYA@mail.gmail.com' \
--to=marth64@proxyid.net \
--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