On Thu, Jan 4, 2024 at 2:38 AM Michael Niedermayer <mich...@niedermayer.cc> wrote:
> On Tue, Jan 02, 2024 at 05:47:53PM +0800, Nuo Mi wrote: > [...] > > maintainer, and any HEVC code change requires a very long review time. > > I think changes that just move code around or rename functions would be > quickly reviewed > I dont know if things are 1:1 identical or some complex changes are needed > > I think if things are 1:1 identical it can be done now otherwise it may be > better to do after the initial merge > Agree, Taking https://patchwork.ffmpeg.org/project/ffmpeg/list/?series=10404 as an example, The following items are worth discussing, though they won't impact the functionality: 1. Can we use "XVC" as a common name for HEVC and VVC, or should we use "h2656" instead of "XVC"? 2. Considering that we will share inter/mc code between VVC and HEVC, do we need to create a new directory for the common code? Sending a separate patch will help us focus on discussions related to code reuse and how to name files This why I suggest we merge the initial patch firstly > thx > > [...] > -- > Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB > > Avoid a single point of failure, be that a person or equipment. > _______________________________________________ > ffmpeg-devel mailing list > ffmpeg-devel@ffmpeg.org > https://ffmpeg.org/mailman/listinfo/ffmpeg-devel > > To unsubscribe, visit link above, or email > ffmpeg-devel-requ...@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-requ...@ffmpeg.org with subject "unsubscribe".
