Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Timo Rothenpieler <timo@rothenpieler.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] Forgejo questions
Date: Thu, 24 Jul 2025 20:03:34 +0200
Message-ID: <176cb314-01a8-4f4e-ad3e-3adba85fa4f4@rothenpieler.org> (raw)
In-Reply-To: <CALbjROJ_LWA6kovbyJ5xBLkaw3NjHh-J_BBaHiyYs2L3YcHJZw@mail.gmail.com>

On 7/24/2025 7:58 PM, Kyle Swanson wrote:
> Hi,
> 
> On Thu, Jul 24, 2025 at 10:46 AM Timo Rothenpieler
> <timo@rothenpieler.org> wrote:
>> The mails will never contain patches, they're just notifications.
>> They do contain a link to the patches and the PR number to fetch it via
>> CLI though.
> 
> If you append ".patch" or ".diff" to the url in the mail, you can get
> the patch/diff directly. Github and Gitlab work in this way also.
> 
> e.g. https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/20027.patch

Yeah, I usually even curl that and pipe it into git am when I'm in a rush.
Though a git alias that properly pulls the PR is also pretty simple.
_______________________________________________
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".

  reply	other threads:[~2025-07-24 18:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-24 17:30 Michael Niedermayer
2025-07-24 17:46 ` Timo Rothenpieler
2025-07-24 17:58   ` Kyle Swanson
2025-07-24 18:03     ` Timo Rothenpieler [this message]
2025-07-25 13:57   ` Michael Niedermayer
2025-07-25 14:19     ` Kieran Kunhya via ffmpeg-devel
2025-07-25 14:30       ` Nicolas George

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=176cb314-01a8-4f4e-ad3e-3adba85fa4f4@rothenpieler.org \
    --to=timo@rothenpieler.org \
    --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