Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Frank Plowman <post@frankplowman.com>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] forgejo PR vs git send email questions
Date: Tue, 29 Jul 2025 08:35:02 +0100
Message-ID: <9a4f0942-8856-47f3-8ecb-ff4057b0df6a@frankplowman.com> (raw)
In-Reply-To: <20250728231307.GK29660@pb2>


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

      parent reply	other threads:[~2025-07-29  7:35 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
2025-07-29 15:48     ` Timo Rothenpieler
2025-07-29  7:35 ` Frank Plowman [this message]

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=9a4f0942-8856-47f3-8ecb-ff4057b0df6a@frankplowman.com \
    --to=post@frankplowman.com \
    --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