Hi Gyan On Tue, Sep 16, 2025 at 10:09:14AM +0530, Gyan Doshi via ffmpeg-devel wrote: > > > On 2025-09-16 03:16 am, Michael Niedermayer via ffmpeg-devel wrote: > > > What can happen is that if an existing open trac issue is taken up for > > > active resolution, then a new issue at Forgejo can be opened, with a > > > reference to the trac issue. A comment can be left at trac linking to this > > > new Forge issue, so all further activity occurs at code.ffmpeg. This would > > > avoid any wholesale migration or duplication. > > It can _IF_ someone spends the extra time and work. > > How many people want to do that ? > > And how many will do it ? > > There's hardly any extra work. > Open a single issue at forge where the title says, "trac 1234: regression in > ..." > Add a link to the trac issue in the body. > Post a comment at the trac issue: "continued at > https://code.ffmpeg.org/FFmpeg/FFmpeg/issues/12345";
Can you show me 10 cases where this has been done ? Or even just one ? Or even just tell me how one could reliably search for issues that continue a trac ticket ? thx [...] -- Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB Those who are best at talking, realize last or never when they are wrong.
signature.asc
Description: PGP signature
_______________________________________________ ffmpeg-devel mailing list -- [email protected] To unsubscribe send an email to [email protected]
