config: deindent all help texts

Those two spaces after tab have no effect, and always a nuisance when editing.

Signed-off-by: Denys Vlasenko <vda.linux@googlemail.com>

4 files changed, 67 insertions, 67 deletions

diff --git a/sysklogd/klogd.c b/sysklogd/klogd.c
index b20d861..728cc8d 100644
--- a/sysklogd/klogd.c
+++ b/sysklogd/klogd.c
@@ -20,11 +20,11 @@
 //config:	bool "klogd (5.5 kb)"
 //config:	default y
 //config:	help
-//config:	  klogd is a utility which intercepts and logs all
-//config:	  messages from the Linux kernel and sends the messages
-//config:	  out to the 'syslogd' utility so they can be logged. If
-//config:	  you wish to record the messages produced by the kernel,
-//config:	  you should enable this option.
+//config:	klogd is a utility which intercepts and logs all
+//config:	messages from the Linux kernel and sends the messages
+//config:	out to the 'syslogd' utility so they can be logged. If
+//config:	you wish to record the messages produced by the kernel,
+//config:	you should enable this option.
 //config:
 //config:comment "klogd should not be used together with syslog to kernel printk buffer"
 //config:	depends on KLOGD && FEATURE_KMSG_SYSLOG
@@ -35,16 +35,16 @@
 //config:	depends on KLOGD
 //config:	select PLATFORM_LINUX
 //config:	help
-//config:	  The klogd applet supports two interfaces for reading
-//config:	  kernel messages. Linux provides the klogctl() interface
-//config:	  which allows reading messages from the kernel ring buffer
-//config:	  independently from the file system.
+//config:	The klogd applet supports two interfaces for reading
+//config:	kernel messages. Linux provides the klogctl() interface
+//config:	which allows reading messages from the kernel ring buffer
+//config:	independently from the file system.
 //config:
-//config:	  If you answer 'N' here, klogd will use the more portable
-//config:	  approach of reading them from /proc or a device node.
-//config:	  However, this method requires the file to be available.
+//config:	If you answer 'N' here, klogd will use the more portable
+//config:	approach of reading them from /proc or a device node.
+//config:	However, this method requires the file to be available.
 //config:
-//config:	  If in doubt, say 'Y'.
+//config:	If in doubt, say 'Y'.
 
 //applet:IF_KLOGD(APPLET(klogd, BB_DIR_SBIN, BB_SUID_DROP))
 
diff --git a/sysklogd/logger.c b/sysklogd/logger.c
index 09fed0c..6769a81 100644
--- a/sysklogd/logger.c
+++ b/sysklogd/logger.c
@@ -11,10 +11,10 @@
 //config:	default y
 //config:	select FEATURE_SYSLOG
 //config:	help
-//config:	    The logger utility allows you to send arbitrary text
-//config:	    messages to the system log (i.e. the 'syslogd' utility) so
-//config:	    they can be logged. This is generally used to help locate
-//config:	    problems that occur within programs and scripts.
+//config:	The logger utility allows you to send arbitrary text
+//config:	messages to the system log (i.e. the 'syslogd' utility) so
+//config:	they can be logged. This is generally used to help locate
+//config:	problems that occur within programs and scripts.
 
 //applet:IF_LOGGER(APPLET(logger, BB_DIR_USR_BIN, BB_SUID_DROP))
 
diff --git a/sysklogd/logread.c b/sysklogd/logread.c
index dd4c7cb..da552e0 100644
--- a/sysklogd/logread.c
+++ b/sysklogd/logread.c
@@ -14,21 +14,21 @@
 //WRONG: it should be compilable without SYSLOG=y:
 //WRONG:	depends on FEATURE_IPC_SYSLOG
 //config:	help
-//config:	  If you enabled Circular Buffer support, you almost
-//config:	  certainly want to enable this feature as well. This
-//config:	  utility will allow you to read the messages that are
-//config:	  stored in the syslogd circular buffer.
+//config:	If you enabled Circular Buffer support, you almost
+//config:	certainly want to enable this feature as well. This
+//config:	utility will allow you to read the messages that are
+//config:	stored in the syslogd circular buffer.
 //config:
 //config:config FEATURE_LOGREAD_REDUCED_LOCKING
 //config:	bool "Double buffering"
 //config:	default y
 //config:	depends on LOGREAD
 //config:	help
-//config:	  'logread' output to slow serial terminals can have
-//config:	  side effects on syslog because of the semaphore.
-//config:	  This option make logread to double buffer copy
-//config:	  from circular buffer, minimizing semaphore
-//config:	  contention at some minor memory expense.
+//config:	'logread' output to slow serial terminals can have
+//config:	side effects on syslog because of the semaphore.
+//config:	This option make logread to double buffer copy
+//config:	from circular buffer, minimizing semaphore
+//config:	contention at some minor memory expense.
 //config:
 
 //applet:IF_LOGREAD(APPLET(logread, BB_DIR_SBIN, BB_SUID_DROP))
diff --git a/sysklogd/syslogd.c b/sysklogd/syslogd.c
index a9c9c69..31730a7 100644
--- a/sysklogd/syslogd.c
+++ b/sysklogd/syslogd.c
@@ -16,53 +16,53 @@
 //config:	bool "syslogd (12 kb)"
 //config:	default y
 //config:	help
-//config:	  The syslogd utility is used to record logs of all the
-//config:	  significant events that occur on a system. Every
-//config:	  message that is logged records the date and time of the
-//config:	  event, and will generally also record the name of the
-//config:	  application that generated the message. When used in
-//config:	  conjunction with klogd, messages from the Linux kernel
-//config:	  can also be recorded. This is terribly useful,
-//config:	  especially for finding what happened when something goes
-//config:	  wrong. And something almost always will go wrong if
-//config:	  you wait long enough....
+//config:	The syslogd utility is used to record logs of all the
+//config:	significant events that occur on a system. Every
+//config:	message that is logged records the date and time of the
+//config:	event, and will generally also record the name of the
+//config:	application that generated the message. When used in
+//config:	conjunction with klogd, messages from the Linux kernel
+//config:	can also be recorded. This is terribly useful,
+//config:	especially for finding what happened when something goes
+//config:	wrong. And something almost always will go wrong if
+//config:	you wait long enough....
 //config:
 //config:config FEATURE_ROTATE_LOGFILE
 //config:	bool "Rotate message files"
 //config:	default y
 //config:	depends on SYSLOGD
 //config:	help
-//config:	  This enables syslogd to rotate the message files
-//config:	  on his own. No need to use an external rotate script.
+//config:	This enables syslogd to rotate the message files
+//config:	on his own. No need to use an external rotate script.
 //config:
 //config:config FEATURE_REMOTE_LOG
 //config:	bool "Remote Log support"
 //config:	default y
 //config:	depends on SYSLOGD
 //config:	help
-//config:	  When you enable this feature, the syslogd utility can
-//config:	  be used to send system log messages to another system
-//config:	  connected via a network. This allows the remote
-//config:	  machine to log all the system messages, which can be
-//config:	  terribly useful for reducing the number of serial
-//config:	  cables you use. It can also be a very good security
-//config:	  measure to prevent system logs from being tampered with
-//config:	  by an intruder.
+//config:	When you enable this feature, the syslogd utility can
+//config:	be used to send system log messages to another system
+//config:	connected via a network. This allows the remote
+//config:	machine to log all the system messages, which can be
+//config:	terribly useful for reducing the number of serial
+//config:	cables you use. It can also be a very good security
+//config:	measure to prevent system logs from being tampered with
+//config:	by an intruder.
 //config:
 //config:config FEATURE_SYSLOGD_DUP
 //config:	bool "Support -D (drop dups) option"
 //config:	default y
 //config:	depends on SYSLOGD
 //config:	help
-//config:	  Option -D instructs syslogd to drop consecutive messages
-//config:	  which are totally the same.
+//config:	Option -D instructs syslogd to drop consecutive messages
+//config:	which are totally the same.
 //config:
 //config:config FEATURE_SYSLOGD_CFG
 //config:	bool "Support syslog.conf"
 //config:	default y
 //config:	depends on SYSLOGD
 //config:	help
-//config:	  Supports restricted syslogd config. See docs/syslog.conf.txt
+//config:	Supports restricted syslogd config. See docs/syslog.conf.txt
 //config:
 //config:config FEATURE_SYSLOGD_READ_BUFFER_SIZE
 //config:	int "Read buffer size in bytes"
@@ -70,23 +70,23 @@
 //config:	range 256 20000
 //config:	depends on SYSLOGD
 //config:	help
-//config:	  This option sets the size of the syslog read buffer.
-//config:	  Actual memory usage increases around five times the
-//config:	  change done here.
+//config:	This option sets the size of the syslog read buffer.
+//config:	Actual memory usage increases around five times the
+//config:	change done here.
 //config:
 //config:config FEATURE_IPC_SYSLOG
 //config:	bool "Circular Buffer support"
 //config:	default y
 //config:	depends on SYSLOGD
 //config:	help
-//config:	  When you enable this feature, the syslogd utility will
-//config:	  use a circular buffer to record system log messages.
-//config:	  When the buffer is filled it will continue to overwrite
-//config:	  the oldest messages. This can be very useful for
-//config:	  systems with little or no permanent storage, since
-//config:	  otherwise system logs can eventually fill up your
-//config:	  entire filesystem, which may cause your system to
-//config:	  break badly.
+//config:	When you enable this feature, the syslogd utility will
+//config:	use a circular buffer to record system log messages.
+//config:	When the buffer is filled it will continue to overwrite
+//config:	the oldest messages. This can be very useful for
+//config:	systems with little or no permanent storage, since
+//config:	otherwise system logs can eventually fill up your
+//config:	entire filesystem, which may cause your system to
+//config:	break badly.
 //config:
 //config:config FEATURE_IPC_SYSLOG_BUFFER_SIZE
 //config:	int "Circular buffer size in Kbytes (minimum 4KB)"
@@ -94,8 +94,8 @@
 //config:	range 4 2147483647
 //config:	depends on FEATURE_IPC_SYSLOG
 //config:	help
-//config:	  This option sets the size of the circular buffer
-//config:	  used to record system log messages.
+//config:	This option sets the size of the circular buffer
+//config:	used to record system log messages.
 //config:
 //config:config FEATURE_KMSG_SYSLOG
 //config:	bool "Linux kernel printk buffer support"
@@ -103,12 +103,12 @@
 //config:	depends on SYSLOGD
 //config:	select PLATFORM_LINUX
 //config:	help
-//config:	  When you enable this feature, the syslogd utility will
-//config:	  write system log message to the Linux kernel's printk buffer.
-//config:	  This can be used as a smaller alternative to the syslogd IPC
-//config:	  support, as klogd and logread aren't needed.
+//config:	When you enable this feature, the syslogd utility will
+//config:	write system log message to the Linux kernel's printk buffer.
+//config:	This can be used as a smaller alternative to the syslogd IPC
+//config:	support, as klogd and logread aren't needed.
 //config:
-//config:	  NOTICE: Syslog facilities in log entries needs kernel 3.5+.
+//config:	NOTICE: Syslog facilities in log entries needs kernel 3.5+.
 
 //applet:IF_SYSLOGD(APPLET(syslogd, BB_DIR_SBIN, BB_SUID_DROP))