From: Michael Niedermayer via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: Michael Niedermayer <michael@niedermayer.cc>
Subject: [FFmpeg-devel] Re: [POLL][VOTE] Preferred Issue Tracker
Date: Tue, 21 Oct 2025 13:03:26 +0200
Message-ID: <aPdofmKfyO-NtRp6@neo> (raw)
In-Reply-To: <fcfd2cd6-3507-4318-b41c-fb06991e500d@lynne.ee>
[-- Attachment #1.1: Type: text/plain, Size: 1096 bytes --]
Hi Lynne
On Tue, Oct 21, 2025 at 04:28:26AM +0200, Lynne via ffmpeg-devel wrote:
[...]
> with issues. I hardly read trac since it has no notifications at all about
> new issues.
There are multiple ways to do this
1.
theres a mailing list that contains all changes to trac including new issues
https://lists.ffmpeg.org/pipermail/ffmpeg-trac/
(its a bit in the middle of mailman2 to mailman3 transition ATM)
2.
https://trac.ffmpeg.org/prefs/notification
you can here set the exact rules when you should be notified
> The lack of a way to ping devs on trac is a HUGE issue.
just click on "Modify Ticket"
and then add to a "," seperated list in "Cc:"
you can add trac usernames but also email addresses
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
The real ebay dictionary, page 1
"Used only once" - "Some unspecified defect prevented a second use"
"In good condition" - "Can be repaird by experienced expert"
"As is" - "You wouldnt want it even if you were payed for it, if you knew ..."
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 163 bytes --]
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org
next prev parent reply other threads:[~2025-10-21 11:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 16:14 [FFmpeg-devel] " Michael Niedermayer via ffmpeg-devel
2025-10-20 16:41 ` [FFmpeg-devel] " Timo Rothenpieler via ffmpeg-devel
2025-10-20 23:30 ` Michael Niedermayer via ffmpeg-devel
2025-10-21 2:28 ` Lynne via ffmpeg-devel
2025-10-21 11:03 ` Michael Niedermayer via ffmpeg-devel [this message]
2025-10-21 11:48 ` Michael Niedermayer via ffmpeg-devel
2025-10-26 22:59 ` Philip Langdale via ffmpeg-devel
2025-10-23 10:49 ` Michael Niedermayer via ffmpeg-devel
2025-10-23 17:41 ` Rémi Denis-Courmont via ffmpeg-devel
2025-10-23 22:01 ` Michael Niedermayer via ffmpeg-devel
2025-10-27 21:02 ` Michael Niedermayer via ffmpeg-devel
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=aPdofmKfyO-NtRp6@neo \
--to=ffmpeg-devel@ffmpeg.org \
--cc=michael@niedermayer.cc \
/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