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] avcodec/vvcdec: move vvcdec.{c, h} to the top directory
Date: Wed, 03 Apr 2024 16:52:35 +0200
Message-ID: <171215595556.30127.3159488504427434175@lain.khirnov.net> (raw)
In-Reply-To: <518aedf1-c113-4f57-8c5b-117ce1af5e02@gmail.com>

Quoting James Almer (2024-04-03 16:46:14)
> On 4/3/2024 5:35 AM, Anton Khirnov wrote:
> > Quoting James Almer (2024-04-02 21:28:28)
> >> On 4/2/2024 4:25 PM, Andreas Rheinhardt wrote:
> >>> James Almer:
> >>>> As it's the main file declaring the AVCodec.
> >>>
> >>> And why is that supposed to be an advantage?
> >>
> >> It's not, it's a cosmetic change. Makes it easier to find at least one
> >> file containing the core code in the base directory.
> >> And I'd like to do the same for other big modules with 3+ source files.
> >> hevc, h264, vp9, etc.
> > 
> > I dislike this.
> 
> Any particular reason why? I'd really like to get some consistency in 
> the lavc folder.

So would I, but it seems inconsistent to me to have everything
foo-related in a directory, except this one special file.

If we have a directory for codec X, it seems most consistent to me to
put EVERYTHING in that directory.

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

  reply	other threads:[~2024-04-03 14:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-02 19:04 James Almer
2024-04-02 19:25 ` Andreas Rheinhardt
2024-04-02 19:28   ` James Almer
2024-04-03  8:35     ` Anton Khirnov
2024-04-03 14:46       ` James Almer
2024-04-03 14:52         ` Anton Khirnov [this message]
2024-04-03 15:39           ` 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=171215595556.30127.3159488504427434175@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