From: Daan De Meyer <daan.j.demeyer@gmail.com>
To: linux-erofs@lists.ozlabs.org
Subject: mkfs.erofs is noisy when run with a pipe attached to stdout/stderr
Date: Tue, 9 Jan 2024 11:12:48 +0100 [thread overview]
Message-ID: <CAO8sHcmnq+foWo7AZYbkxJXHfSeZkd73Dq+1dQSZYBE6QxL8JQ@mail.gmail.com> (raw)
Hi,
When executed with a pipe attached to stdout/stderr (for example in
CI), mkfs.erofs is super verbose as \r doesn't go to the beginning of
the line so mkfs.erofs will print a separate line for each file in the
root directory that is passed to mkfs.erofs. Could mkfs.erofs be
updated to not print a separate line for each file when stdout/stderr
are not ttys?
Cheers,
Daan De Meyer
next reply other threads:[~2024-01-09 10:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-09 10:12 Daan De Meyer [this message]
2024-01-09 13:10 ` mkfs.erofs is noisy when run with a pipe attached to stdout/stderr Gao Xiang
2024-01-16 4:26 ` [PATCH] erofs-utils: avoid noisy prints if stdout is not a tty Gao Xiang
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=CAO8sHcmnq+foWo7AZYbkxJXHfSeZkd73Dq+1dQSZYBE6QxL8JQ@mail.gmail.com \
--to=daan.j.demeyer@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).