From: "Dawid Kozinski/Multimedia \(PLT\) /SRPOL/Staff Engineer/Samsung Electronics" <d.kozinski@samsung.com>
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: Wed, 15 Feb 2023 09:50:38 +0100
Message-ID: <00ca01d9411a$9464f620$bd2ee260$@samsung.com> (raw)
In-Reply-To: <NOG4SvS--3-9@lynne.ee>
-----Original Message-----
From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of Lynne
Sent: wtorek, 14 lutego 2023 19:01
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
Feb 14, 2023, 13:10 by d.kozinski@samsung.com:
>
> -----Original Message-----
> From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of
> Lynne
> Sent: poniedziałek, 13 lutego 2023 18:32
> 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
>
> Feb 13, 2023, 10:29 by d.kozinski@samsung.com:
>
>> Lynne, if it concerns us, we will comply with both the current and
>> the new maintainership policy once your patchset is pushed. We see
>> that your change has not yet been pushed into the main branch, and it
>> appears that the discussion on this topic may still be ongoing,
>> although both Michael and other maintainers have reviewed and
>> commented on
>>
> it.
>
>>
>>
>
> What do you mean both current and new policy?
>
> Lynne, you mentioned a new policy change on maintainership in one of
> the previous emails:
> "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."
>
Fair enough, I'll just review the patchset while ignoring this patch.
Dear Lynne,
Thank you for your response. I really appreciate your willingness to review the patchset, and I I'm looking forward to hearing your feedback. I understand that this patch may present some challenges, since it's a quite big, but I believe that with your guidance, we can finally come up with a solution that meets FFmpeg requirements.
Thank you again for taking the time to review the patchset. We will be eagerly awaiting your feedback.
Best regards,
Dawid
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://protect2.fireeye.com/v1/url?k=c6da1d34-a6388069-c6db967b-000babd9f1ba-f1087034b8a00e05&q=1&e=f6840520-ddf5-4d1d-890b-9f658856ac36&u=https%3A%2F%2Fffmpeg.org%2Fmailman%2Flistinfo%2Fffmpeg-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".
next prev parent reply other threads:[~2023-02-15 8:50 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
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 [this message]
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='00ca01d9411a$9464f620$bd2ee260$@samsung.com' \
--to=d.kozinski@samsung.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