Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: patches via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: Michael Niedermayer <michael@niedermayer.cc>,
	FFmpeg development discussions and patches
	<ffmpeg-devel@ffmpeg.org>
Cc: patches <patches@vector.com>
Subject: Re: [FFmpeg-devel] [PATCH] avdevice/dshow: Don't skip audio devices if no video device is present
Date: Wed, 24 Jul 2024 07:09:45 +0000
Message-ID: <DBBPR01MB10433E463B34EE92842880A44F0AA2@DBBPR01MB10433.eurprd01.prod.exchangelabs.com> (raw)
In-Reply-To: <20240723202136.GE4991@pb2>



-----Original Message-----
From: Michael Niedermayer <michael@niedermayer.cc> 
Sent: Tuesday, July 23, 2024 10:22 PM
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: patches <patches@vector.com>
Subject: Re: [FFmpeg-devel] [PATCH] avdevice/dshow: Don't skip audio devices if no video device is present

On Tue, Jul 23, 2024 at 08:21:31AM +0000, patches via ffmpeg-devel wrote:
> 
> -----Original Message-----
> From: Roger Pack <rogerdpack2@gmail.com>
> Sent: Monday, July 22, 2024 5:52 PM
> To: patches <patches@vector.com>
> Cc: FFmpeg development discussions and patches 
> <ffmpeg-devel@ffmpeg.org>
> Subject: Re: [FFmpeg-devel] [PATCH] avdevice/dshow: Don't skip audio 
> devices if no video device is present
> 
> On Wed, Jul 17, 2024 at 1:43 AM patches <patches@vector.com> wrote:
> >
> > -----Original Message-----
> > From: ffmpeg-devel <ffmpeg-devel-bounces@ffmpeg.org> On Behalf Of 
> > Roger Pack
> > Sent: Wednesday, July 17, 2024 3:03 AM
> > To: FFmpeg development discussions and patches 
> > <ffmpeg-devel@ffmpeg.org>
> > Subject: Re: [FFmpeg-devel] [PATCH] avdevice/dshow: Don't skip audio 
> > devices if no video device is present
> >
> > > LGTM
> >
> > I also need this fix in 5.1 release branch, is this possible?
> 
> > Not sure how backports work, but you could make your own fork with it in it?
> 
> Can someone at least commit the fix on the main line?

> What should be put in the "Author" metadata for this ?

> I can put "patches <patches@vector.com>" in it if thats really intended but it looks like it may be unintended, so iam asking

Please use "Jens Frederich". We have a general mailbox for patches at Vector and I can't put a name there, I'll see if I can do better next time when I create a patch. 

Michael, will there be another 5.x release? If so, is it possible to apply the patch there? We are currently using 5.1 and the changeover to 6.x or 7.x is not foreseeable.

_______________________________________________
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:[~2024-07-24  7:09 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-15  6:51 patches via ffmpeg-devel
2024-07-17  1:02 ` Roger Pack
2024-07-17  7:43   ` patches via ffmpeg-devel
2024-07-22 15:51     ` Roger Pack
2024-07-23  8:15       ` patches via ffmpeg-devel
2024-07-23  8:21       ` patches via ffmpeg-devel
2024-07-23 20:21         ` Michael Niedermayer
2024-07-24  7:09           ` patches via ffmpeg-devel [this message]
2024-07-24 12:33             ` Michael Niedermayer
2024-07-22  5:27   ` patches via ffmpeg-devel

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=DBBPR01MB10433E463B34EE92842880A44F0AA2@DBBPR01MB10433.eurprd01.prod.exchangelabs.com \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=michael@niedermayer.cc \
    --cc=patches@vector.com \
    /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