From: Coywolf Qi Hunt <qiyong@fc-cn.com>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] small Kconfig help text correction for CONFIG_FRAME_POINTER
Date: Wed, 12 Oct 2005 09:25:28 +0800 [thread overview]
Message-ID: <20051012012528.GA2845@localhost.localdomain> (raw)
In-Reply-To: <200510112322.22004.jesper.juhl@gmail.com>
On Tue, Oct 11, 2005 at 11:22:21PM +0200, Jesper Juhl wrote:
> Fix-up the CONFIG_FRAME_POINTER help text language a bit.
>
> Signed-off-by: Jesper Juhl <jesper.juhl@gmail.com>
> ---
>
> "on some architectures or you use external debuggers"
> doesn't sound too good
> "on some architectures or if you use external debuggers"
> is better.
Why bother anyway since the original is brief and neat. (yours could be s/if/when/ even)
Coywolf
>
> lib/Kconfig.debug | 4 ++--
> 1 files changed, 2 insertions(+), 2 deletions(-)
>
> --- linux-2.6.14-rc4-orig/lib/Kconfig.debug 2005-10-11 22:41:32.000000000 +0200
> +++ linux-2.6.14-rc4/lib/Kconfig.debug 2005-10-11 23:16:30.000000000 +0200
> @@ -174,7 +174,7 @@
> default y if DEBUG_INFO && UML
> help
> If you say Y here the resulting kernel image will be slightly larger
> - and slower, but it might give very useful debugging information
> - on some architectures or you use external debuggers.
> + and slower, but it might give very useful debugging information on
> + some architectures or if you use external debuggers.
> If you don't debug the kernel, you can say N.
>
>
>
> -
next prev parent reply other threads:[~2005-10-12 1:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-11 21:22 [PATCH] small Kconfig help text correction for CONFIG_FRAME_POINTER Jesper Juhl
2005-10-12 1:25 ` Coywolf Qi Hunt [this message]
2005-10-12 1:50 ` Felix Oxley
2005-10-12 10:45 ` Jesper Juhl
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=20051012012528.GA2845@localhost.localdomain \
--to=qiyong@fc-cn.com \
--cc=akpm@osdl.org \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.