Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Nicolas George via ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Cc: "Kacper Michajłow" <code@ffmpeg.org>, "Nicolas George" <george@nsup.org>
Subject: [FFmpeg-devel] Re: [PATCH] avutil/opt: support DOS paths in key value parser (PR #21008)
Date: Thu, 4 Dec 2025 15:23:18 +0100
Message-ID: <aTGZVtSToLq8sms6@phare.normalesup.org> (raw)
In-Reply-To: <176401638706.39.15034261601653496028@2cb04c0e5124>

Kacper Michajłow via ffmpeg-devel (HE12025-11-24):
> PR #21008 opened by Kacper Michajłow (kasper93)
> URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21008
> Patch URL: https://code.ffmpeg.org/FFmpeg/FFmpeg/pulls/21008.patch
> 
> This allow to pass DOS path in filter graph string. Although we use `:`
> as separator, we can make an exception for DOS path looking string. In
> which cases first `:` is allowed to be included in the value.
> 
> Fixes drawvg filter, which would otherwise fail to parse `file` option
> when DOS path is provided.
> 

I am strongly against this, it makes the parsing erratic and requires
weird special cases in code that generate options strings.

Let users escape their paths.

> Fixes: fate-filter-drawvg-video

If the problematic paths come from FATE, then fix FATE to escape paths.

Regards,

-- 
  Nicolas George
_______________________________________________
ffmpeg-devel mailing list -- ffmpeg-devel@ffmpeg.org
To unsubscribe send an email to ffmpeg-devel-leave@ffmpeg.org

      reply	other threads:[~2025-12-04 14:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-24 20:33 [FFmpeg-devel] " Kacper Michajłow via ffmpeg-devel
2025-12-04 14:23 ` Nicolas George via ffmpeg-devel [this message]

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=aTGZVtSToLq8sms6@phare.normalesup.org \
    --to=ffmpeg-devel@ffmpeg.org \
    --cc=code@ffmpeg.org \
    --cc=george@nsup.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