From: "Namjae Jeon" <namjae.jeon@samsung.com>
To: "'Linux Kernel Mailing List'" <linux-kernel@vger.kernel.org>,
<linux-fsdevel@vger.kernel.org>
Cc: "'Eric Sandeen'" <sandeen@sandeen.net>,
"'Goldwyn Rodrigues'" <rgoldwyn@suse.com>,
"'Nicolas Boos'" <nicolas.boos@wanadoo.fr>,
<sedat.dilek@gmail.com>, "'Hyunchul Lee'" <hyc.lee@gmail.com>,
"'Luca Stefani'" <luca.stefani.ge1@gmail.com>,
"'Matthieu CASTET'" <castet.matthieu@free.fr>,
"'Sven Hoexter'" <sven@stormbind.net>,
"'Ethan Sommer'" <e5ten.arch@gmail.com>,
"'Ethan Sommer'" <e5ten.arch@gmail.com>,
"'Hyeongseok Kim'" <hyeongseok@gmail.com>
Subject: [ANNOUNCE] exfatprogs-1.1.0 version released
Date: Wed, 10 Feb 2021 08:50:46 +0900 [thread overview]
Message-ID: <000001d6ff3e$62f336d0$28d9a470$@samsung.com> (raw)
In-Reply-To: CGME20210209235046epcas1p1416b5b121c0d78bfcb854aab46ea35c2@epcas1p1.samsung.com
Hi folk,
We have released exfatprogs 1.1.0 version. In this release, exfatlabel
has been added to print or re-write volume label and volume serial value.
Also, A new dump.exfat util has been added to display statistics from
a given device(Requested by Mike Fleetwood(GParted Developer)).
Any feedback is welcome!:)
CHANGES :
* fsck.exfat: Recover corrupted boot region.
NEW FEATURES :
* exfatlabel: Print or set volume label and serial.
* dump.exfat: Show the on-disk metadata information and the statistics.
BUG FIXES :
* Set _FILE_OFFSET_BITS=64 for Android build.
The git tree is at:
https://github.com/exfatprogs/exfatprogs
The tarballs can be found at:
https://github.com/exfatprogs/exfatprogs/releases/download/1.1.0/exfatprogs-1.1.0.tar.gz
next parent reply other threads:[~2021-02-10 0:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210209235046epcas1p1416b5b121c0d78bfcb854aab46ea35c2@epcas1p1.samsung.com>
2021-02-09 23:50 ` Namjae Jeon [this message]
2021-02-10 3:37 ` [ANNOUNCE] exfatprogs-1.1.0 version released Sedat Dilek
2021-02-10 4:51 ` Namjae Jeon
2021-02-10 7:24 ` Sedat Dilek
2021-02-10 9:27 ` Sedat Dilek
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='000001d6ff3e$62f336d0$28d9a470$@samsung.com' \
--to=namjae.jeon@samsung.com \
--cc=castet.matthieu@free.fr \
--cc=e5ten.arch@gmail.com \
--cc=hyc.lee@gmail.com \
--cc=hyeongseok@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca.stefani.ge1@gmail.com \
--cc=nicolas.boos@wanadoo.fr \
--cc=rgoldwyn@suse.com \
--cc=sandeen@sandeen.net \
--cc=sedat.dilek@gmail.com \
--cc=sven@stormbind.net \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).