Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: jfrederich <jfrederich@proton.me>
Subject: Re: [FFmpeg-devel] [RFC] patch for LTS release
Date: Sun, 30 Jun 2024 01:44:54 +0200
Message-ID: <20240629234454.GD4991@pb2> (raw)
In-Reply-To: <Lu-xExVHwVNrQEDA9l5MKPOY-JQfxPMRkkT3NcrqAFww6TEbI9bqV3DWFTFf7qUZN5X86x1iFvauAEogZAvAiRpuOPB878_lLm4qKhCwpfM=@proton.me>


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

On Thu, Jun 27, 2024 at 07:11:28AM +0000, jfrederich via ffmpeg-devel wrote:
> Hello,
> 
> we have found a minor bug in dshow.c that we would like to submit as a patch. Is it possible to submit a patch for 5.1.x LTS? Do I have to consider anything special for this?

If the bug is fixed in master and not in release/5.1 then the fix from master needs to be backported to release/5.1
    In this case please tell us which commit needs to be backported

If the bug is not fixed in master then please submit a patch against git master first

thx

[...]
-- 
Michael     GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB

I know you won't believe me, but the highest form of Human Excellence is
to question oneself and others. -- Socrates

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

      parent reply	other threads:[~2024-06-29 23:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-27  7:11 jfrederich via ffmpeg-devel
2024-06-27  7:46 ` Jean-Baptiste Kempf
2024-06-29 23:44 ` Michael Niedermayer [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=20240629234454.GD4991@pb2 \
    --to=michael@niedermayer.cc \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=jfrederich@proton.me \
    /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