Linux-EROFS Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gao Xiang <hsiangkao@linux.alibaba.com>
To: "Luke T. Shumaker" <lukeshu@lukeshu.com>, linux-erofs@lists.ozlabs.org
Cc: "Luke T. Shumaker" <lukeshu@umorpha.io>
Subject: Re: [PATCH 0/3] erofs-utils: Address doc and flag-parsing snags
Date: Sun, 5 Nov 2023 20:51:27 +0800	[thread overview]
Message-ID: <43fc745e-581d-e0a5-7198-c070ae99a85b@linux.alibaba.com> (raw)
In-Reply-To: <20231102193122.140921-1-lukeshu@lukeshu.com>



On 2023/11/3 03:31, Luke T. Shumaker wrote:
> From: "Luke T. Shumaker" <lukeshu@umorpha.io>
> 
> Hi all,
> 
> This patchset addresses snags that I hit while adopting erofs for our
> system images.
> 
>   - The first patch is really just setting a baseline for the next two.
> 
>   - The second patch is improving the --help text to address the snag
>     that I had to read the source code to understand how to use the
>     mkfs.erofs `-z` flag, and also setting the stage for the third
>     patch.  In doing this I broadly improved the --help text overall,
>     not just for mkfs.erofs.
> 
>   - The third patch is adding no-op `-a`, `-A`, and `-y` flags to
>     fsck.erofs, to address the snag that I was seeing errors in the
>     boot scroll.
> 
> I didn't touch erofsfuse in any of these, not because it isn't worthy
> of the changes from the first two patches, just that I decided it
> would have been too much work at the moment.

Thanks, applied for testing.

Thanks,
Gao Xiang

> 
> Luke T. Shumaker (3):
>    erofs-utils: have each non-fuse command take -h, --help, -V, and
>      --version
>    erofs-utils: improve the usage and version text of non-fuse commands
>    erofs-utils: fsck: Add -a, -A, and -y flags
> 
>   dump/main.c              |  47 +++++++------
>   fsck/main.c              |  81 ++++++++++++++--------
>   include/erofs/compress.h |   2 +-
>   lib/compressor.c         |  13 +---
>   lib/compressor.h         |   9 ++-
>   man/dump.erofs.1         |   5 +-
>   man/fsck.erofs.1         |   8 ++-
>   man/mkfs.erofs.1         |  15 ++--
>   mkfs/main.c              | 144 +++++++++++++++++++++++++--------------
>   9 files changed, 202 insertions(+), 122 deletions(-)
> 

      parent reply	other threads:[~2023-11-05 12:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-02 19:31 [PATCH 0/3] erofs-utils: Address doc and flag-parsing snags Luke T. Shumaker
2023-11-02 19:31 ` [PATCH 1/3] erofs-utils: have each non-fuse command take -h, --help, -V, and --version Luke T. Shumaker
2023-11-02 19:31 ` [PATCH 2/3] erofs-utils: improve the usage and version text of non-fuse commands Luke T. Shumaker
2023-11-02 19:31 ` [PATCH 3/3] erofs-utils: fsck: Add -a, -A, and -y flags Luke T. Shumaker
2023-11-05 12:51 ` Gao Xiang [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=43fc745e-581d-e0a5-7198-c070ae99a85b@linux.alibaba.com \
    --to=hsiangkao@linux.alibaba.com \
    --cc=linux-erofs@lists.ozlabs.org \
    --cc=lukeshu@lukeshu.com \
    --cc=lukeshu@umorpha.io \
    /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