From: "Theodore Ts'o" <tytso@mit.edu>
To: Jan Kara <jack@suse.cz>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH 3/9] e2image: Dump quota files
Date: Tue, 3 Aug 2021 12:15:39 -0400 [thread overview]
Message-ID: <YQlrq40wmMMYO9YP@mit.edu> (raw)
In-Reply-To: <20210616105735.5424-4-jack@suse.cz>
On Wed, Jun 16, 2021 at 12:57:29PM +0200, Jan Kara wrote:
> Dump quota files to resulting filesystem image. They are fs metadata.
>
> Signed-off-by: Jan Kara <jack@suse.cz>
Thanks, applied to the maint branch.
- Ted
next prev parent reply other threads:[~2021-08-03 16:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 10:57 [PATCH 0/9 v3] e2fsprogs: Support for orphan file feature Jan Kara
2021-06-16 10:57 ` [PATCH 1/9] ext2fs: Drop HAS_SNAPSHOT feature Jan Kara
2021-06-16 10:57 ` [PATCH 2/9] quota: Do not account space used by project quota file to quota Jan Kara
2021-08-03 16:13 ` Theodore Ts'o
2021-08-04 12:15 ` Jan Kara
2021-06-16 10:57 ` [PATCH 3/9] e2image: Dump quota files Jan Kara
2021-08-03 16:15 ` Theodore Ts'o [this message]
2021-06-16 10:57 ` [PATCH 4/9] libext2fs: Support for orphan file feature Jan Kara
2021-08-03 17:36 ` Theodore Ts'o
2021-08-03 17:57 ` Theodore Ts'o
2021-06-16 10:57 ` [PATCH 5/9] mke2fs: Add support for orphan_file feature Jan Kara
2021-06-16 10:57 ` [PATCH 6/9] e2fsck: Add support for handling orphan file Jan Kara
2021-06-16 10:57 ` [PATCH 7/9] tune2fs: Add support for orphan_file feature Jan Kara
2021-06-16 10:57 ` [PATCH 8/9] mke2fs: Add orphan_file feature into mke2fs.conf Jan Kara
2021-06-16 10:57 ` [PATCH 9/9] dumpe2fs, debugfs, e2image: Add support for orphan file Jan Kara
-- strict thread matches above, loose matches on Subject: below --
2021-07-12 15:43 [PATCH 0/9 v4] e2fsprogs: Support for orphan file feature Jan Kara
2021-07-12 15:43 ` [PATCH 3/9] e2image: Dump quota files Jan Kara
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=YQlrq40wmMMYO9YP@mit.edu \
--to=tytso@mit.edu \
--cc=jack@suse.cz \
--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).