Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Pierre-Anthony Lemieux <pal@sandflow.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] MAINTAINERS: add maintainer for the imf demuxer
Date: Thu, 15 Sep 2022 17:03:12 -0700
Message-ID: <CAF_7JxCANNtkAZkE=zVvFA6pDgAr8dRC0qR0c5x3FkodZ=Ai5A@mail.gmail.com> (raw)
In-Reply-To: <NC2OwwV--3-2@lynne.ee>

On Thu, Sep 15, 2022 at 4:07 PM Lynne <dev@lynne.ee> wrote:
>
> Sep 16, 2022, 00:46 by pal@sandflow.com:
>
> > From: Pierre-Anthony Lemieux <pal@palemieux.com>
> >
> > ---
> >  MAINTAINERS | 2 ++
> >  1 file changed, 2 insertions(+)
> >
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index ed2ec0b90c..2d37f0b86a 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -436,6 +436,7 @@ Muxers/Demuxers:
> >  idcin.c                               Mike Melanson
> >  idroqdec.c                            Mike Melanson
> >  iff.c                                 Jaikrishnan Menon
> > +  imf*                                  Pierre-Anthony Lemieux
> >  img2*.c                               Michael Niedermayer
> >  ipmovie.c                             Mike Melanson
> >  ircam*                                Paul B Mahol
> > @@ -633,6 +634,7 @@ Nikolay Aleksandrov           8978 1D8C FB71 588E 4B27 EAA8 C4F0 B5FC E011 13B1
> >  Panagiotis Issaris            6571 13A3 33D9 3726 F728 AA98 F643 B12E ECF3 E029
> >  Peter Ross                    A907 E02F A6E5 0CD2 34CD 20D2 6760 79C5 AC40 DD6B
> >  Philip Langdale               5DC5 8D66 5FBA 3A43 18EC 045E F8D6 B194 6A75 682E
> > +Pierre-Anthony Lemieux (pal)  F4B3 9492 E6F2 E4AF AEC8 46CB 698F A1F0 F8D4 EED4
> >  Ramiro Polla                  7859 C65B 751B 1179 792E DAE8 8E95 8B2F 9B6C 5700
> >  Reimar Doeffinger             C61D 16E5 9E2C D10C 8958 38A4 0899 A2B9 06D4 D9C7
> >  Reinhard Tartler              9300 5DC2 7E87 6C37 ED7B CA9A 9808 3544 9453 48A4
> >
>
> That list is for those with push access. Are you sure you want that?

You make it sound unpleasant :)

In all seriousness, my objective is being responsive to issues filed
against the IMF demuxer.

I am happy to set aside the time to be a maintainer if it helps
achieve that objective.

I am also happy to not be a maintainer if it will not help.

> We don't have strict requirements for that, but you're just past
> the #commits to get a vote on TC questions.
> Reviewing patches takes a while, but that's just how it is when
> they're of little interest to most.

Yes.

Isn't this particularly true when there is no maintainer for that
module -- as is currently the case for the IMF demuxer?

On a related note, I would think that review of narrow bug fixes like
[1] would require relatively less time than, say, the addition of an
imf muxer.

[1] https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=7416

In any case thanks for your help/input since the beginning of my
involvement with the codebase.

> _______________________________________________
> 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:[~2022-09-16  0:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-15 22:46 pal
2022-09-15 23:07 ` Lynne
2022-09-16  0:03   ` Pierre-Anthony Lemieux [this message]
2022-09-16  6:37     ` Paul B Mahol
2022-09-16 11:05 ` Michael Niedermayer

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='CAF_7JxCANNtkAZkE=zVvFA6pDgAr8dRC0qR0c5x3FkodZ=Ai5A@mail.gmail.com' \
    --to=pal@sandflow.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