From: Tobias Rapp <t.rapp@noa-archive.com> To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>, ffmpegagent <ffmpegagent@gmail.com> Cc: "Martin Storsjö" <martin@martin.st>, softworkz <softworkz@hotmail.com> Subject: Re: [FFmpeg-devel] [PATCH v3 0/2] use av_fopen_utf8() instead of plain fopen() Date: Tue, 17 May 2022 13:56:23 +0200 Message-ID: <d3efb623-3329-d3f7-6554-82a41f92d5d3@noa-archive.com> (raw) In-Reply-To: <pull.26.v3.ffstaging.FFmpeg.1652747942.ffmpegagent@gmail.com> On 17/05/2022 02:39, ffmpegagent wrote: > Unify file access operations by replacing usages of direct calls to posix > fopen() As the cover letter will be gone after commit I think it would be a good idea to add the reason for the change also in the commit messages directly. Is this in preparation for the long filename support on Windows? Then maybe this could be mentioned, too. > v2: Remove changes to fftools for now > v3: Add some additional replacements > > softworkz (2): > avfilter: use av_fopen_utf8() instead of plain fopen() > avfilter/dvdsubdec: use av_fopen_utf8() instead of plain fopen() Patch #2 title should start with "avcodec/dvdsubdec: ..." I guess. > > libavcodec/dvdsubdec.c | 2 +- > libavfilter/af_firequalizer.c | 2 +- > libavfilter/vf_deshake.c | 2 +- > libavfilter/vf_psnr.c | 2 +- > libavfilter/vf_signature.c | 4 ++-- > libavfilter/vf_ssim.c | 2 +- > libavfilter/vf_vidstabdetect.c | 2 +- > libavfilter/vf_vidstabtransform.c | 2 +- > libavfilter/vf_vmafmotion.c | 2 +- > 9 files changed, 10 insertions(+), 10 deletions(-) > > [...] Regards, Tobias _______________________________________________ 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-05-17 11:56 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-07 17:39 [FFmpeg-devel] [PATCH " ffmpegagent 2022-05-07 17:39 ` [FFmpeg-devel] [PATCH 1/2] fftools: " softworkz 2022-05-08 20:03 ` Martin Storsjö 2022-05-09 0:21 ` Soft Works 2022-05-07 17:39 ` [FFmpeg-devel] [PATCH 2/2] avfilter: " softworkz 2022-05-09 18:52 ` [FFmpeg-devel] [PATCH v2] " softworkz 2022-05-10 20:12 ` Martin Storsjö 2022-05-10 23:03 ` Soft Works 2022-05-17 0:39 ` [FFmpeg-devel] [PATCH v3 0/2] " ffmpegagent 2022-05-17 0:39 ` [FFmpeg-devel] [PATCH v3 1/2] avfilter: " softworkz 2022-05-17 0:39 ` [FFmpeg-devel] [PATCH v3 2/2] avfilter/dvdsubdec: " softworkz 2022-05-17 11:56 ` Tobias Rapp [this message] 2022-05-17 12:26 ` [FFmpeg-devel] [PATCH v3 0/2] " Soft Works 2022-05-17 12:29 ` [FFmpeg-devel] [PATCH v4 " ffmpegagent 2022-05-17 12:29 ` [FFmpeg-devel] [PATCH v4 1/2] avfilter: " softworkz 2022-05-17 12:29 ` [FFmpeg-devel] [PATCH v4 2/2] avcodec/dvdsubdec: " softworkz 2022-05-18 7:01 ` [FFmpeg-devel] [PATCH v4 0/2] " Tobias Rapp 2022-05-19 21:39 ` Soft Works 2022-05-19 21:40 ` [FFmpeg-devel] [PATCH v5 0/3] " ffmpegagent 2022-05-19 21:40 ` [FFmpeg-devel] [PATCH v5 1/3] avfilter: " softworkz 2022-05-19 21:40 ` [FFmpeg-devel] [PATCH v5 2/3] avcodec/dvdsubdec: " softworkz 2022-05-19 21:40 ` [FFmpeg-devel] [PATCH v5 3/3] avfilter: Make avpriv_open a library-internal function on msvcrt softworkz 2022-05-19 23:15 ` [FFmpeg-devel] [PATCH v6 0/3] use av_fopen_utf8() instead of plain fopen() ffmpegagent 2022-05-19 23:15 ` [FFmpeg-devel] [PATCH v6 1/3] avfilter: " softworkz 2022-05-19 23:15 ` [FFmpeg-devel] [PATCH v6 2/3] avcodec/dvdsubdec: " softworkz 2022-05-19 23:15 ` [FFmpeg-devel] [PATCH v6 3/3] avfilter: Make avpriv_open a library-internal function on msvcrt softworkz 2022-05-23 11:26 ` [FFmpeg-devel] [PATCH v7 0/2] use av_fopen_utf8() instead of plain fopen() ffmpegagent 2022-05-23 11:26 ` [FFmpeg-devel] [PATCH v7 1/2] avfilter: " softworkz 2022-05-23 11:26 ` [FFmpeg-devel] [PATCH v7 2/2] avcodec/dvdsubdec: " softworkz 2022-05-24 8:55 ` [FFmpeg-devel] [PATCH v7 0/2] " Martin Storsjö
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=d3efb623-3329-d3f7-6554-82a41f92d5d3@noa-archive.com \ --to=t.rapp@noa-archive.com \ --cc=ffmpeg-devel@ffmpeg.org \ --cc=ffmpegagent@gmail.com \ --cc=martin@martin.st \ --cc=softworkz@hotmail.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