From: "Theodore Ts'o" <tytso@mit.edu>
To: Alexey Lyashkov <alexey.lyashkov@gmail.com>
Cc: linux-ext4@vger.kernel.org, Andreas Dilger <adilger@dilger.ca>,
Artem Blagodarenko <artem.blagodarenko@gmail.com>
Subject: Re: [PATCH] e2fsprogs: avoid code duplication
Date: Wed, 3 Aug 2022 15:58:14 -0400 [thread overview]
Message-ID: <YurTVlGWqwym2Hgg@mit.edu> (raw)
In-Reply-To: <20220803075407.538398-1-alexey.lyashkov@gmail.com>
On Wed, Aug 03, 2022 at 10:54:07AM +0300, Alexey Lyashkov wrote:
> debugfs and e2fsck have a so much code duplication in journal handing.
> debugfs have lack a many journal features handing also.
> Let's start code merging to avoid code duplication and lack features.
This is definitely worth doing, and as you've pointed out, there are a
number of features which are in e2fsck/journal.c, which are not in
debugfs/journal.c. The most notable one which I picked up on is the
fast_commit code --- which is in the master/next branch, but not in
the maint branch.
I suggest that we move the functionality into the libsupport library
first. I want to make sure we get the abstractions right before we
"cast them into stone" by moving the functions to libext2fs.
Libsupport is not exported outside of e2fsprogs, so if we decide we
want to change function signatures, or make some functions private, we
can do that more easily if we experiment with moving things into
libsupport first.
- Ted
next prev parent reply other threads:[~2022-08-03 19:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-03 7:54 [PATCH] e2fsprogs: avoid code duplication Alexey Lyashkov
2022-08-03 16:39 ` Lukas Czerner
2022-08-03 17:00 ` Alexey Lyahkov
2022-08-03 19:58 ` Theodore Ts'o [this message]
2022-08-03 21:52 ` Alexey Lyahkov
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=YurTVlGWqwym2Hgg@mit.edu \
--to=tytso@mit.edu \
--cc=adilger@dilger.ca \
--cc=alexey.lyashkov@gmail.com \
--cc=artem.blagodarenko@gmail.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