From: Gao Xiang <xiang@kernel.org>
To: Benjamin Drung <bdrung@posteo.de>
Cc: Gao Xiang <hsiangkao@linux.alibaba.com>, linux-erofs@lists.ozlabs.org
Subject: Re: [PATCH] erofs-utils: manpage: document missing --quiet option for mkfs.erofs
Date: Thu, 12 Feb 2026 09:26:04 +0800 [thread overview]
Message-ID: <aY0sLFNqwhGY17av@debian> (raw)
In-Reply-To: <2ee1ac1a6072f92c80b817e3413b0610f802bc6d.camel@posteo.de>
Hi Benjamin,
On Wed, Feb 11, 2026 at 05:48:38PM +0000, Benjamin Drung wrote:
> On Wed, 2026-02-11 at 02:28 +0800, Gao Xiang wrote:
> > Reported-by: Benjamin Drung <bdrung@posteo.de>
> > Closes: https://github.com/erofs/erofs-utils/issues/36
> > Signed-off-by: Gao Xiang <hsiangkao@linux.alibaba.com>
> > ---
> > man/mkfs.erofs.1 | 3 +++
> > 1 file changed, 3 insertions(+)
> >
> > diff --git a/man/mkfs.erofs.1 b/man/mkfs.erofs.1
> > index cc5a3109ac7f..4316214ff1e2 100644
> > --- a/man/mkfs.erofs.1
> > +++ b/man/mkfs.erofs.1
> > @@ -240,6 +240,9 @@ Use extended inodes instead of compact inodes if the file modification time
> > would overflow compact inodes. This is the default. Overrides
> > .BR --ignore-mtime .
> > .TP
> > +.B "\-\-quiet"
> > +Quiet execution (do not write anything to standard output.)
> > +.TP
> > .BI "\-\-sort=" MODE
> > Inode data sorting order for tarballs as input.
> >
>
> Does mkfs.erofs also support the short version -q?
Nope.. generally long options are preferred unless the functionalities
are vitally important so that it deserve a short version (I don't want
to have arbitary option list from `a` to `z`, also if some common
alphabet is used for an uncommon usage, it will be hard to remove or
switch to a more useful usage.)
Thanks,
Gao Xiang
>
> --
> Benjamin Drung
> Debian & Ubuntu Developer
>
prev parent reply other threads:[~2026-02-12 1:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-10 18:28 [PATCH] erofs-utils: manpage: document missing --quiet option for mkfs.erofs Gao Xiang
2026-02-11 17:48 ` Benjamin Drung
2026-02-12 1:26 ` 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=aY0sLFNqwhGY17av@debian \
--to=xiang@kernel.org \
--cc=bdrung@posteo.de \
--cc=hsiangkao@linux.alibaba.com \
--cc=linux-erofs@lists.ozlabs.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
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