Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Lynne <dev@lynne.ee>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v14 9/9] avcodec/evc: Changes in Changelog and MAINTAINERS files
Date: Mon, 30 Jan 2023 00:18:22 +0100 (CET)
Message-ID: <NMzolTf--3-9@lynne.ee> (raw)
In-Reply-To: <20230129095713.GI1949656@pb2>

Jan 29, 2023, 10:57 by michael@niedermayer.cc:

> Hi
>
> On Fri, Jan 27, 2023 at 01:03:00PM +0100, Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics wrote:
>
>> Hi,
>> It's been almost a month since we submitted our latest changes to the FFmpeg patchwork. I know that EVC implementation isn't the only thing you are working on at the moment but we'd like to do another step forward, toward merging our implementation into the master branch of the FFmpeg repository. 
>> The contribution is something that we take seriously so we'd like to finally do some progress.
>> We would like to merge it as soon as it is enough good and it meets the expected quality. Continual synchronization of our changes with the latest FFmpeg changes and splitting our changes into patches is, let's say a painstaking job. It would be much easier to develop and refine the code if we could skip that hard splitting on patches step that we have to do each time we do any, even small change.
>> We know that the new FFmpeg version will be released soon and you may be absorbed and overwhelmed with the work related to the new release. However, we'd be grateful if you found a little time and take a look at our latest changes.
>> Last but not least. Do you have any plans related to including such changes as our EVC implementation in the next release?
>>
>
> I cannot speak for others but ATM for me its difficult to add this patchset to my
> todo list. If someone reviews and applies it it could make it in for the release
> but will anyone, i do not know.
> What i can say is that if a patch which adds you to MAINTAINERS is applied ping me
> and ill give you git write (unless there are some new standing objections), 
> and once you have that you can work on this code with less pain. 
> But i will leave applying the MAINTAINERS change to others too
> as some people seemed not happy anout it and i think in such case its better if a 2nd
> developer does that
>
> PS: Maybe you can troll the people who didnt like your MAINTAINERS addition into
> reviewing & applying your patchset. Its not an unreasonable request because if
> you dont have git write someone else has to apply changes
>

I assign myself to personally review the patchset and push it, if you review my policy
change on maintainership. As I said, I have no objection on who gets maintainership,
just that it is done explicitly via a separate list in the maintainers file.
_______________________________________________
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:[~2023-01-29 23:18 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20221024074233eucas1p125b43125cce202641bf48d0f174a39a1@eucas1p1.samsung.com>
2022-10-24  7:42 ` Dawid Kozinski
2022-10-24 15:56   ` Lynne
2022-10-24 16:29     ` James Almer
2022-10-25 11:17       ` Lynne
2022-10-27 16:45         ` Michael Niedermayer
2022-10-28 21:08           ` Lynne
2022-12-13 12:22             ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics
2022-12-13 13:33               ` Ronald S. Bultje
2022-12-14 13:02                 ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics
2022-12-14 21:36                 ` Michael Niedermayer
2022-12-15  9:14                   ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics
2022-12-15 19:22                     ` Michael Niedermayer
2023-01-27 12:03                       ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics
2023-01-29  9:57                         ` Michael Niedermayer
2023-01-29 23:18                           ` Lynne [this message]
2023-02-06  8:46                             ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics
2023-02-13  9:28                             ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics
2023-02-13 17:32                               ` Lynne
2023-02-14 12:10                                 ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics
2023-02-14 18:00                                   ` Lynne
2023-02-15  8:50                                     ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics
2023-03-06 10:46                                     ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics
2023-03-18 17:53                                       ` Lynne
2023-03-21  9:22                                         ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics
2023-02-14 18:03                                   ` Kieran Kunhya
2023-02-15  8:49                                     ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics
2023-02-15 13:05                                       ` Kieran Kunhya
2023-02-16  8:49                                         ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics
2023-01-02 13:07                   ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics
2022-12-13 18:42               ` Lynne
2022-12-14 12:54                 ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics
2022-12-14 21:45                 ` Michael Niedermayer
2022-12-15  1:11                   ` Lynne
2022-12-15 19:15                     ` 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=NMzolTf--3-9@lynne.ee \
    --to=dev@lynne.ee \
    --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