From: Dave Chinner <david@fromorbit.com>
To: fstests@vger.kernel.org
Subject: [PATCH 0/2] common: make common/rc easier to manage
Date: Wed, 30 Nov 2016 08:32:31 +1100 [thread overview]
Message-ID: <20161129213233.8462-1-david@fromorbit.com> (raw)
Hi folks,
common/rc has grown huge with lots of library functions, and it's
becoming hard to manage. The following two patches split the XFS and
btrfs specific functionality in common/rc into separate files which
are sourced directly from common/rc based on $FSTYP.
This moves a large chunk of code spread throughout common/rc into
smaller, more contained files where it is easier to see how the
filesystem specific pieces are put together. I'd like to see this
happen for other filesytems, and quite possibly other groups of
functionality that make sense to manage separately.
Thoughts and comments welcome!
-Dave.
next reply other threads:[~2016-11-29 21:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-29 21:32 Dave Chinner [this message]
2016-11-29 21:32 ` [PATCH 1/2] common: split XFS functions from common/rc Dave Chinner
2016-11-29 23:24 ` Darrick J. Wong
2016-11-29 21:32 ` [PATCH 2/2] common: split Btrfs " Dave Chinner
2016-11-30 10:10 ` [PATCH 0/2] common: make common/rc easier to manage Eryu Guan
2016-11-30 21:11 ` Dave Chinner
2016-12-01 4:18 ` Eryu Guan
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=20161129213233.8462-1-david@fromorbit.com \
--to=david@fromorbit.com \
--cc=fstests@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