From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH 0/2] e2scrub: fix some problems
Date: Sat, 9 Nov 2019 22:37:22 -0500 [thread overview]
Message-ID: <20191110033722.GE23325@mit.edu> (raw)
In-Reply-To: <157291884852.328601.5452592601628272222.stgit@magnolia>
On Mon, Nov 04, 2019 at 05:54:08PM -0800, Darrick J. Wong wrote:
> Hi all,
>
> Fix a couple of problems that have been reported against e2scrub_all.
> The first fixes a complaint about a large increase in boot time due to
> automatic reaping of e2scrub snapshots. The second eliminates some
> broken hackery around loop iteration in bash.
>
> This is an extraordinary way to destroy everything. Enjoy!
> Comments and questions are, as always, welcome.
Thanks, look good. I've applied this to the e2fsprogs maint branch.
- Ted
prev parent reply other threads:[~2019-11-10 3:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 1:54 [PATCH 0/2] e2scrub: fix some problems Darrick J. Wong
2019-11-05 1:54 ` [PATCH 1/2] e2scrub_all: don't even reap if the config file doesn't allow it Darrick J. Wong
2019-11-05 1:54 ` [PATCH 2/2] e2scrub_all: fix broken stdin redirection Darrick J. Wong
2019-11-10 3:37 ` Theodore Y. Ts'o [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=20191110033722.GE23325@mit.edu \
--to=tytso@mit.edu \
--cc=darrick.wong@oracle.com \
--cc=linux-ext4@vger.kernel.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 NNTP newsgroup(s).