Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Anton Khirnov <anton@khirnov.net>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] lavc: move bitstream filters into bsf/ subdir
Date: Fri, 26 Jan 2024 13:17:35 +0100
Message-ID: <170627145523.8914.14993136855646933607@lain.khirnov.net> (raw)
In-Reply-To: <Np4ffE6--3-9@lynne.ee>

Quoting Lynne (2024-01-26 13:11:33)
> Jan 26, 2024, 11:40 by anton@khirnov.net:
> 
> > ---
> >  libavcodec/Makefile                           | 49 +---------------
> >  libavcodec/bsf/Makefile                       | 56 +++++++++++++++++++
> >
> 
> Is that the general direction we want to take?
> I don't mind it, but I'm wondering if I should do this for what I care about?

I'd say yes for things with >~ 10 files. libavcodec/ got way too large.

-- 
Anton Khirnov
_______________________________________________
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-01-26 12:17 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-26 10:39 Anton Khirnov
2024-01-26 12:11 ` Lynne
2024-01-26 12:17   ` Zhao Zhili
2024-01-26 12:17   ` Anton Khirnov [this message]
2024-01-26 16:09     ` James Almer
2024-01-26 16:17       ` Anton Khirnov
2024-01-26 16:22         ` James Almer
2024-01-26 16:24           ` Anton Khirnov
2024-01-26 12:35 ` Andreas Rheinhardt
2024-01-26 16:22   ` Anton Khirnov
2024-01-28 17:49   ` Anton Khirnov
2024-01-29  9:57     ` Andreas Rheinhardt
2024-01-29 10:21       ` Anton Khirnov
2024-01-29 10:55         ` Andreas Rheinhardt
2024-01-29 11:07           ` Anton Khirnov
2024-01-29 11:15           ` Anton Khirnov
2024-01-29 11:29             ` Andreas Rheinhardt

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=170627145523.8914.14993136855646933607@lain.khirnov.net \
    --to=anton@khirnov.net \
    --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