Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Romain Beauxis <romain.beauxis@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2] ogg/vorbis: implement header packet skip in chained ogg bitstreams.
Date: Mon, 28 Jul 2025 16:12:13 -0500
Message-ID: <CABWZ6ORkNRDd3cEYLBjT4qactar79yObt-dhG11T3itgjYRq_w@mail.gmail.com> (raw)
In-Reply-To: <20250728002212.GX29660@pb2>

Le dim. 27 juil. 2025 à 19:22, Michael Niedermayer <michael@niedermayer.cc>
a écrit :
>
> Hi Romain
>
> On Wed, Jul 23, 2025 at 02:06:07PM -0500, Romain Beauxis wrote:
> > Le sam. 21 juin 2025 à 16:59, Michael Niedermayer <
michael@niedermayer.cc>
> > a écrit :
> > >
> > > On Sat, Jun 21, 2025 at 10:45:32AM +0200, Romain Beauxis wrote:
> > > > Le dim. 15 juin 2025 à 00:57, Michael Niedermayer
> > > > <michael@niedermayer.cc> a écrit :
> > > > >
> > > > > On Wed, Jun 04, 2025 at 11:58:52AM -0500, Romain Beauxis wrote:
> > > > > > This is a redo of 574f634e49847e2225ee50013afebf0de03ef013
using a
> > flat
> > > > > > memory storage for the extradata.
> > > > > >
> > > > > > PR review comments addressed:
> > > > > > * Use flat memory bytestream
> > > > > > * Re-use existing xiph extradata layout
> > > > > >
> > > > > > ---
> > > > >
> > > > > >  libavcodec/vorbisdec.c                     | 42 ++++++++---
> > > > > >  libavformat/oggparsevorbis.c               | 83
> > +++++++++++++++++++++-
> > > > >
> > > > > patches that change both libraries at the same time are suspect
> > > > >
> > > > > if one depends on changes in the other it needs
> > > > > minor API version bump and seperate patches so extension of
> > > > > API and use of it are properly tracked and testable
> > > >
> > > > If I remember well, according to Andreas Rheinhardt there's no need
> > > > for an API bump here since the patch is re-using existing extradata
> > > > bitstream structures.
> > >
> > > If there is really no API extension then the micro versions should be
> > bumped
> > > so a user knows if the specific version he uses has teh fix.
> > > Also it may be usefull in bugreports about ogg to know if its prior or
> > > after this change
> >
> > Hi Michael,
> >
> > I have created a PR on code.ffmpeg.org here:
> > https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20026
> >
>
> > Would you have a minute to have a look?
>
> I do not have time, ive made a dumb mistake in configuring my inbox
> so iam about a week behind with emails without realizing it.
> thats on top of release, security, and other things
>
> maybe someome else can look into this one
> replying here so noone waits for a review from me

Thanks for letting me know and sorry about your issues with your email
inbox.

Do you have any advice on how to look for a reviewer for this path?

> thx
>
> [...]
> --
> Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
>
> Any man who breaks a law that conscience tells him is unjust and willingly
> accepts the penalty by staying in jail in order to arouse the conscience
of
> the community on the injustice of the law is at that moment expressing the
> very highest respect for law. - Martin Luther King Jr
> _______________________________________________
> 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".
_______________________________________________
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".

      reply	other threads:[~2025-07-28 21:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-04 16:58 Romain Beauxis
2025-06-10 18:04 ` Romain Beauxis
2025-06-12 11:35   ` Michael Niedermayer
2025-06-14 10:39     ` Romain Beauxis
2025-06-14 22:57 ` Michael Niedermayer
2025-06-21  8:45   ` Romain Beauxis
2025-06-21 21:59     ` Michael Niedermayer
2025-07-23 19:06       ` Romain Beauxis
2025-07-28  0:22         ` Michael Niedermayer
2025-07-28 21:12           ` Romain Beauxis [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=CABWZ6ORkNRDd3cEYLBjT4qactar79yObt-dhG11T3itgjYRq_w@mail.gmail.com \
    --to=romain.beauxis@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