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>
Cc: '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: Sat, 18 Mar 2023 18:53:13 +0100 (CET)
Message-ID: <NQpqebo--3-9@lynne.ee> (raw)
In-Reply-To: <005601d95018$eba226d0$c2e67470$@samsung.com>

Mar 6, 2023, 11:46 by d.kozinski@samsung.com:

>
>
>
>> -----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,
>
> I just wanted to timidly remind you that we are still waiting for a review of our code.
> Please have mercy on us and don't let us wait for ages. We don't want to wait indefinitely, and we would like to move forward with our project.
>

Ping, I sent a review of the patchset more than a week ago,
could you look into fixing the issues?
Like I said in my review, the issues aren't huge, just some
cleanups and timebase/timestamp issues.
_______________________________________________
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-03-18 17:53 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
2023-03-06 10:46                                     ` Dawid Kozinski/Multimedia (PLT) /SRPOL/Staff Engineer/Samsung Electronics
2023-03-18 17:53                                       ` Lynne [this message]
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=NQpqebo--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