From: Gao Xiang via Linux-erofs <firstname.lastname@example.org> To: email@example.com, firstname.lastname@example.org Cc: Lasse Collin <email@example.com>, LKML <firstname.lastname@example.org>, Miao Xie <email@example.com> Subject: [ANNOUNCE] erofs-utils: release 1.1 Date: Tue, 14 Apr 2020 00:46:08 +0800 [thread overview] Message-ID: <20200413164544.GA5578@hsiangkao-HP-ZHAN-66-Pro-G1> (raw) In-Reply-To: <20200413164544.GA5578.ref@hsiangkao-HP-ZHAN-66-Pro-G1> Hi folks, A new version erofs-utils 1.1 is available at: git://git.kernel.org/pub/scm/linux/kernel/git/xiang/erofs-utils.git tags/v1.1 It's actually a maintenance release including the following updates: - (mkfs.erofs) add a manual for mkfs.erofs; - (mkfs.erofs) add superblock checksum support; - (mkfs.erofs) add filesystem UUID support; - (mkfs.erofs) add exclude files support; - (mkfs.erofs) fix compiling issues under some specific conditions, mainly reported by various buildbots; - (mkfs.erofs) minor code cleanups; EROFS LZMA support is still ongoing, and the previous preliminary progress is available at https://firstname.lastname@example.org and https://email@example.com some minor updates I'd like to send out with the next WIP version. In addition, as discussed with Lasse before, XZ Utils liblzma would probably support fixed-sized output compression officially later as well. But it may need some more time then. Recently I have little time for features due to struggling with my upcoming English test which has been greatly impacted (delayed) by corona. While I'm still keeping up with community by email and available for all potential issues and/or responses if any. Thanks, Gao Xiang
parent reply other threads:[~2020-04-13 16:49 UTC|newest] Thread overview: expand[flat|nested] mbox.gz Atom feed [parent not found: <20200413164544.GA5578.ref@hsiangkao-HP-ZHAN-66-Pro-G1>]
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=20200413164544.GA5578@hsiangkao-HP-ZHAN-66-Pro-G1 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [ANNOUNCE] erofs-utils: release 1.1' \ /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
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).