From f4f1f33f8b9a3d74bd592895a5779e91f1a2e8cd Mon Sep 17 00:00:00 2001 From: Jujuforce Date: Mon, 6 Jul 2026 22:13:24 +0200 Subject: [PATCH] chore: repoint exfat-fs patch to the v0.1.3-tag-based fix commit The exfat-fs empty-file fix branch was rebuilt on top of the upstream v0.1.3 release tag (instead of an orphan commit) so it has proper shared history and reads as a clean "1 commit ahead of v0.1.3". Update the pinned rev accordingly; tree and behavior are identical (v0.1.3 + the one-function fix). Co-Authored-By: Claude Opus 4.8 --- Cargo.lock | 2 +- Cargo.toml | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/Cargo.lock b/Cargo.lock index e8a9cef..01ea53c 100644 --- a/Cargo.lock +++ b/Cargo.lock @@ -481,7 +481,7 @@ dependencies = [ [[package]] name = "exfat-fs" version = "0.1.3" -source = "git+https://github.com/jujuforce/exfat-fs.git?rev=7067f6afe3c21d9c737288475b29e5dae790e206#7067f6afe3c21d9c737288475b29e5dae790e206" +source = "git+https://github.com/jujuforce/exfat-fs.git?rev=dc50d0539246a91f08ad01b565e408f7f94136b6#dc50d0539246a91f08ad01b565e408f7f94136b6" dependencies = [ "bitflags", "bytemuck", diff --git a/Cargo.toml b/Cargo.toml index 4b4ff39..8a9a375 100644 --- a/Cargo.toml +++ b/Cargo.toml @@ -27,7 +27,7 @@ strip = "none" # empty file legitimately has FirstCluster = 0 / DataLength = 0. That aborts # the whole extraction the moment an OPTION container contains any 0-byte file. # Until the fix lands in a published release, override with a fork branch that -# is the 0.1.3 release plus only that one-function fix (identical public API). +# is the v0.1.3 release tag plus only that one-function fix (identical public API). # See https://github.com/jujuforce/exfat-fs/tree/v0.1.3-empty-file-fix [patch.crates-io] -exfat-fs = { git = "https://github.com/jujuforce/exfat-fs.git", rev = "7067f6afe3c21d9c737288475b29e5dae790e206" } +exfat-fs = { git = "https://github.com/jujuforce/exfat-fs.git", rev = "dc50d0539246a91f08ad01b565e408f7f94136b6" }