Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
* [FFmpeg-devel] forgejo PR vs git send email questions
@ 2025-07-28 23:13 Michael Niedermayer
  2025-07-28 23:14 ` James Almer
  2025-07-29  7:35 ` Frank Plowman
  0 siblings, 2 replies; 5+ messages in thread
From: Michael Niedermayer @ 2025-07-28 23:13 UTC (permalink / raw)
  To: FFmpeg development discussions and patches


[-- Attachment #1.1: Type: text/plain, Size: 574 bytes --]

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


-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

I have never wished to cater to the crowd; for what I know they do not
approve, and what they approve I do not know. -- Epicurus

[-- 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".

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [FFmpeg-devel] forgejo PR vs git send email questions
  2025-07-28 23:13 [FFmpeg-devel] forgejo PR vs git send email questions Michael Niedermayer
@ 2025-07-28 23:14 ` James Almer
  2025-07-29 12:51   ` Michael Niedermayer
  2025-07-29  7:35 ` Frank Plowman
  1 sibling, 1 reply; 5+ messages in thread
From: James Almer @ 2025-07-28 23:14 UTC (permalink / raw)
  To: ffmpeg-devel


[-- Attachment #1.1.1: Type: text/plain, Size: 523 bytes --]

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.


[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 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".

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [FFmpeg-devel] forgejo PR vs git send email questions
  2025-07-28 23:13 [FFmpeg-devel] forgejo PR vs git send email questions Michael Niedermayer
  2025-07-28 23:14 ` James Almer
@ 2025-07-29  7:35 ` Frank Plowman
  1 sibling, 0 replies; 5+ messages in thread
From: Frank Plowman @ 2025-07-29  7:35 UTC (permalink / raw)
  To: ffmpeg-devel


[-- Attachment #1.1.1.1: Type: text/plain, Size: 642 bytes --]

On 29/07/2025 00:13, 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
> 

If they might be merged independently of one another, it's best if
they're put in separate PRs as merging on the web interface does not
allow for merging only some commits from a PR.

-- 
Frank

[-- Attachment #1.1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 1091 bytes --]

[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 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".

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [FFmpeg-devel] forgejo PR vs git send email questions
  2025-07-28 23:14 ` James Almer
@ 2025-07-29 12:51   ` Michael Niedermayer
  2025-07-29 15:48     ` Timo Rothenpieler
  0 siblings, 1 reply; 5+ messages in thread
From: Michael Niedermayer @ 2025-07-29 12:51 UTC (permalink / raw)
  To: FFmpeg development discussions and patches


[-- 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".

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: [FFmpeg-devel] forgejo PR vs git send email questions
  2025-07-29 12:51   ` Michael Niedermayer
@ 2025-07-29 15:48     ` Timo Rothenpieler
  0 siblings, 0 replies; 5+ messages in thread
From: Timo Rothenpieler @ 2025-07-29 15:48 UTC (permalink / raw)
  To: ffmpeg-devel

On 7/29/2025 2:51 PM, Michael Niedermayer wrote:
> 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 ?

On the right side of each issue/pr site.

> 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

They'll need an account in order for you to be able to do that.

> ATM, it seems i have to send 2 emails manually for this

You'll need to mail them a link to the issue/pr manually if they don't 
have an account, yes.

> thx
> 
> [...]
> 
> 
> _______________________________________________
> 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".

_______________________________________________
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".

^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2025-07-29 15:48 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2025-07-28 23:13 [FFmpeg-devel] forgejo PR vs git send email questions Michael Niedermayer
2025-07-28 23:14 ` James Almer
2025-07-29 12:51   ` Michael Niedermayer
2025-07-29 15:48     ` Timo Rothenpieler
2025-07-29  7:35 ` Frank Plowman

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