PR #7 opened by qaq03101 URL: https://code.ffmpeg.org/FFmpeg/web/pulls/7 Patch URL: https://code.ffmpeg.org/FFmpeg/web/pulls/7.patch
The bug reporting page still directs users to Trac and its registration page, although new reports are handled on Forgejo. Users can therefore register on the old tracker only to be redirected to a different service. Point the page directly to the current Forgejo issue tracker and provide Forgejo registration and sign-in links. Tested with: - `make htdocs/bugreports.html` - `git diff --check upstream/master...HEAD` Fixes FFmpeg/FFmpeg#22833. >From d7ed019c07728fb71d28d68c79958104b7cda624 Mon Sep 17 00:00:00 2001 From: qaq03101 <[email protected]> Date: Thu, 16 Jul 2026 15:10:02 +0800 Subject: [PATCH] web/bugreports: point to Forgejo issue tracker Signed-off-by: qaq03101 <[email protected]> --- src/bugreports | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/src/bugreports b/src/bugreports index f8c2581..51f8f01 100644 --- a/src/bugreports +++ b/src/bugreports @@ -111,11 +111,12 @@ info all-registers</pre> <p> Once you have gathered this information, you can submit a report to the - <a href="https://trac.ffmpeg.org";>FFmpeg bug tracker</a>. + <a href="https://code.ffmpeg.org/FFmpeg/FFmpeg/issues";>FFmpeg bug tracker</a>. </p> <p> - <i>Note, you must <a href="https://trac.ffmpeg.org/register";>register</a> - there first before you can submit a report.</i> + <i>Note, you must <a href="https://code.ffmpeg.org/user/sign_up";>register</a> + or <a href="https://code.ffmpeg.org/user/login";>sign in</a> before you can + submit a report.</i> </p> <p> You should provide all information so that anyone can reproduce the bug.<br> -- 2.52.0 _______________________________________________ ffmpeg-devel mailing list -- [email protected] To unsubscribe send an email to [email protected]
