From: Ridley Combs <rcombs@rcombs.me>
To: ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 2/2] fftools: enable long path support on Windows
Date: Wed, 8 Mar 2023 15:43:52 -0600
Message-ID: <9159B000-441A-485A-9F8C-0986A4B4EF15@rcombs.me> (raw)
In-Reply-To: <691276b7-cdf1-ce1d-79a6-a0d2744d2a4d@martin.st>
> On Mar 8, 2023, at 15:35, Martin Storsjö <martin@martin.st> wrote:
>
> On Wed, 8 Mar 2023, rcombs wrote:
>
>> This allows use of filesystem paths longer than MAX_PATH (260 characters)
>> on Windows 10 version 1607 and later.
>>
>> This _may_ be a no-op if a "LongPathsEnabled" isn't set in the registry.
>> ---
>> fftools/fftools.manifest | 1 +
>> 1 file changed, 1 insertion(+)
>
> Are you aware of the changes in c5aba39a041fdaac267fc8c6a2ef745a94a2b0da last year? That was supposed to make this change redundant, and make long paths usable even on versions of Windows older than that.
>
> // Martin
I hadn't seen that change, but I do think it's still worth signaling our support for long paths explicitly.
>
> _______________________________________________
> 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".
_______________________________________________
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".
prev parent reply other threads:[~2023-03-08 21:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 21:27 [FFmpeg-devel] [PATCH 1/2] fftools: set process code page to UTF-8 " rcombs
2023-03-08 21:27 ` [FFmpeg-devel] [PATCH 2/2] fftools: enable long path support " rcombs
2023-03-08 21:35 ` Martin Storsjö
2023-03-08 21:43 ` Ridley Combs [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=9159B000-441A-485A-9F8C-0986A4B4EF15@rcombs.me \
--to=rcombs@rcombs.me \
--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