From: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v9 2/7] e2fsprogs: add help text for all config options
Date: Sun, 23 Apr 2017 00:49:14 +0200 [thread overview]
Message-ID: <20170422224919.3257-3-arnout@mind.be> (raw)
In-Reply-To: <20170422224919.3257-1-arnout@mind.be>
From: Carlos Santos <casantos@datacom.ind.br>
Signed-off-by: Carlos Santos <casantos@datacom.ind.br>
Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
---
package/e2fsprogs/Config.in | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/package/e2fsprogs/Config.in b/package/e2fsprogs/Config.in
index 676327dc2f..23c4db5329 100644
--- a/package/e2fsprogs/Config.in
+++ b/package/e2fsprogs/Config.in
@@ -23,14 +23,20 @@ if BR2_PACKAGE_E2FSPROGS
config BR2_PACKAGE_E2FSPROGS_DEBUGFS
bool "debugfs"
+ help
+ ext2/ext3/ext4 file system debugger
config BR2_PACKAGE_E2FSPROGS_E2IMAGE
bool "e2image"
+ help
+ Save critical ext2/ext3/ext4 filesystem metadata to a file
config BR2_PACKAGE_E2FSPROGS_E4DEFRAG
bool "e4defrag"
depends on !BR2_nios2 # fallocate not implemented
depends on !BR2_TOOLCHAIN_USES_UCLIBC # sync_file_range not impl
+ help
+ Online defragmenter for ext4 filesystem
comment "e4defrag needs a glibc or musl toolchain"
depends on !BR2_nios2
@@ -39,17 +45,24 @@ comment "e4defrag needs a glibc or musl toolchain"
config BR2_PACKAGE_E2FSPROGS_FSCK
bool "fsck"
default y
+ help
+ Check and repair a Linux file system. This is a wrapper around
+ the filesystem-specific fsck tools.
config BR2_PACKAGE_E2FSPROGS_FUSE2FS
bool "fuse2fs"
depends on !BR2_STATIC_LIBS # libfuse
depends on BR2_TOOLCHAIN_HAS_THREADS # libfuse
select BR2_PACKAGE_LIBFUSE
+ help
+ FUSE file system client for ext2/ext3/ext4 file systems
comment "fuse2fs needs a toolchain w/ threads, dynamic library"
depends on !BR2_TOOLCHAIN_HAS_THREADS || BR2_STATIC_LIBS
config BR2_PACKAGE_E2FSPROGS_RESIZE2FS
bool "resize2fs"
+ help
+ ext2/ext3/ext4 file system resizer
endif
--
2.11.0
next prev parent reply other threads:[~2017-04-22 22:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-22 22:49 [Buildroot] [PATCH v9 0/7] e2fsprogs: refactor to fix conflicts with busybox and util-linux Arnout Vandecappelle
2017-04-22 22:49 ` [Buildroot] [PATCH v9 1/7] " Arnout Vandecappelle
2017-04-22 22:49 ` Arnout Vandecappelle [this message]
2017-04-22 22:49 ` [Buildroot] [PATCH v9 3/7] e2fsprogs: disable unneeded features for host Arnout Vandecappelle
2017-04-22 22:49 ` [Buildroot] [PATCH v9 4/7] e2fsprogs: add explicit --enable/--disable configure options Arnout Vandecappelle
2017-04-22 22:49 ` [Buildroot] [PATCH v9 5/7] e2fsprogs: avoid conflict with util-linux fsck wrapper Arnout Vandecappelle
2017-04-22 22:49 ` [Buildroot] [PATCH v9 6/7] e2fsprogs: only add -lintl for static builds Arnout Vandecappelle
2017-04-22 22:49 ` [Buildroot] [PATCH v9 7/7] e2fsprogs: add empty lines to .mk file Arnout Vandecappelle
2017-05-04 20:37 ` [Buildroot] [PATCH v9 0/7] e2fsprogs: refactor to fix conflicts with busybox and util-linux Thomas Petazzoni
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=20170422224919.3257-3-arnout@mind.be \
--to=arnout@mind.be \
--cc=buildroot@busybox.net \
/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