From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] forgejo PR vs git send email questions
Date: Tue, 29 Jul 2025 14:51:50 +0200
Message-ID: <20250729125150.GL29660@pb2> (raw)
In-Reply-To: <1240b54f-4b7a-4da1-a86b-1627d4415e21@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1229 bytes --]
On Mon, Jul 28, 2025 at 08:14:58PM -0300, James Almer wrote:
> On 7/28/2025 8:13 PM, Michael Niedermayer wrote:
> > Hi
> >
> > with git send email i can send 5 independant patches with
> >
> > git send-email --to='FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>' -5
> >
> > and have some CC: tags to make sure people
> > (like bug reporter or security researcher) get notified
> >
> > Does our forgejo act on CC: ?
> >
> > Also with 5 independant patches, 1 pr or 5 prs ?
> >
> > thx
>
> On PRs you can tag people or assign them as reviewers, which will notify
> them.
How do i do that ?
I mean someone lets say donald@duck.com mails me a security issue or even a patch
once i have a patch that fixes the issue, he should be informed that the patch is
now on the tracker, and further he should be informated when the pr is applied
of course the person has no account on forgejo
ATM, it seems i have to send 2 emails manually for this
thx
[...]
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
When you are offended at any man's fault, turn to yourself and study your
own failings. Then you will forget your anger. -- Epictetus
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2025-07-29 12:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-28 23:13 Michael Niedermayer
2025-07-28 23:14 ` James Almer
2025-07-29 12:51 ` Michael Niedermayer [this message]
2025-07-29 15:48 ` Timo Rothenpieler
2025-07-29 7:35 ` Frank Plowman
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=20250729125150.GL29660@pb2 \
--to=michael@niedermayer.cc \
--cc=ffmpeg-devel@ffmpeg.org \
/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