> Yes but there was only a day and a half between v2_2 and my comments, and > that's way too short.
Hi, the timing feels a bit unclear here because it's v2_2, not v3, as I only resolved the conflict (#elif ARCH_WASM was newly added) and made no other changes. Rémi Denis-Courmont <r...@remlab.net> 于2024年12月31日周二 02:26写道： > Le tiistaina 24. joulukuuta 2024, 15.30.00 EET Nuo Mi a écrit : > > On Mon, Dec 23, 2024 at 11:18 PM flow gg <hlefthl...@gmail.com> wrote: > > > Hi, It looks like you submitted your review comments not long after the > > > patch was merged. > > > > > > Previously, regarding the VVC avg patch, you mentioned "LGTM for the > > > RISC-V > > > side. No clue about the VVC side", > > > so I contacted Nuomi in the hope that he could help merge the patch > that > > > had been pending for a while. > > > > Hi Remi, > > Yes, v2 has been on the mailing list for about two weeks. > > Yes but there was only a day and a half between v2_2 and my comments, and > that's way too short. > > > I also shared > > that I planned to merge it within two days. > > > https://patchwork.ffmpeg.org/project/ffmpeg/patch/tencent_EA1C0DCD17B7CD3960 > > e58735f274a82a5...@qq.com/#89698 Are there any best practices to avoid > such > > situations in the future? Would it be better if you handled merging all > > RISC-V code? > > The first thing to do is switch to Gitlab to alleviate the review and > tracking > burden. > > With that said, I'm all for sharing the code review burden with somebody > else, > if they have the time, expertise and attention to do so. Unfortunately, > while > there are several other RISC-V-capable developers here, none of them seem > really both willing and able to review Sunyuechi (or my) patches. > > -- > Rémi Denis-Courmont > http://www.remlab.net/ > > > > _______________________________________________ > 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".
