From: "Ronald S. Bultje" <rsbultje@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] avcodec/x86/Makefile: Don't build empty files
Date: Tue, 13 Dec 2022 15:13:04 -0500
Message-ID: <CAEEMt2k0dTaCtLts7RNW2o=ZfgBTZNJvj82_CfgK4_+fWzR+xQ@mail.gmail.com> (raw)
In-Reply-To: <CAB0OVGq2Uyd9TW_C+uxQDCxNHqurx5U_bVvkoXPkP0uzUYGV4A@mail.gmail.com>
Hi,
On Tue, Dec 13, 2022 at 2:12 PM Carl Eugen Hoyos <ceffmpeg@gmail.com> wrote:
> It does.
> (I did not consider this an issue when I saw it.)
>
> I consider this unmaintainable, an argument that in the past was
> used to object significantly more important patches (in cases
> where maintenance was imo no problem).
>
> Anyway: No objection.
>
It's not that it's a big deal, just that it's mildly annoying and there
doesn't appear to be an obvious downside to fixing it.
Ronald
_______________________________________________
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".
next prev parent reply other threads:[~2022-12-13 20:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-11 14:17 [FFmpeg-devel] [PATCH]lavc/x86/simple_idct: Fix linking shared libavcodec with MS link.exe Carl Eugen Hoyos
2022-09-11 14:19 ` Carl Eugen Hoyos
2022-09-11 14:26 ` James Almer
2022-09-11 14:21 ` Carl Eugen Hoyos
2022-09-11 15:29 ` Andreas Rheinhardt
2022-09-11 17:15 ` Carl Eugen Hoyos
2022-09-12 15:04 ` [FFmpeg-devel] [PATCH] avcodec/x86/Makefile: Don't build empty files Andreas Rheinhardt
2022-09-15 22:03 ` Carl Eugen Hoyos
2022-09-15 22:12 ` Andreas Rheinhardt
2022-12-13 15:02 ` Andreas Rheinhardt
2022-12-13 18:54 ` Carl Eugen Hoyos
2022-12-13 19:03 ` Andreas Rheinhardt
2022-12-13 19:11 ` Carl Eugen Hoyos
2022-12-13 20:13 ` Ronald S. Bultje [this message]
2022-10-20 7:04 ` [FFmpeg-devel] [PATCH]lavc/x86/simple_idct: Fix linking shared libavcodec with MS link.exe 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='CAEEMt2k0dTaCtLts7RNW2o=ZfgBTZNJvj82_CfgK4_+fWzR+xQ@mail.gmail.com' \
--to=rsbultje@gmail.com \
--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