From: Roland Eggner <edvx1@systemanalysen.net>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: linux-kbuild@vger.kernel.org,
Dmitry Voytik <dvv.kernel@gmail.com>,
Michal Marek <mmarek@suse.cz>,
Stephen Boyd <sboyd@codeaurora.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH resend v3 1/3] kconfig: nconf: rewrite help texts
Date: Sun, 10 Feb 2013 04:00:30 +0100 [thread overview]
Message-ID: <20130210030030.GA20308@mobil.systemanalysen.net> (raw)
In-Reply-To: <201302091223.36881.yann.morin.1998@free.fr>
[-- Attachment #1: Type: text/plain, Size: 1190 bytes --]
On 2013-02-09 Saturday at 12:23 +0100 Yann E. MORIN wrote:
> Rolland, All,
>
> On Saturday 09 February 2013 Roland Eggner wrote:
> > On 2013-02-09 Saturday at 01:30 +0100 Yann E. MORIN wrote:
> [--SNIP--]
> > > > +"Text Box (Help Window)\n"
> > > > +"----------------------\n"
> > > > +"Use movement keys <Down> <Up> <PageDown> <PageUp> <End> <Home> as listed in\n"
> > > > +"table above.\n"
> > >
> > > ... keys [elided] as listed ...
> >
> > Ok, because you are dropping patch 3/3.
>
> If that was related to patch 3/3, that should have been in that patch,
> not this one.
My “Ok, because …” referred to your “keys [elided] as listed …” in that
particular hunk, whereas my “You performed a nice polish …” several hunks later
referred to the whole patch. Just to avoid misunderstanding.
>
> [--SNIP--]
> > > Any reason for the re-indent with one more space?
> >
> > Intention is optimization for fast reading, as usual in professional text
> > processing: seperate words by single space; separate sentences, half-sentences
> > and listing symbols by two spaces.
>
> OK, I kept it.
Thank you.
--
Regards
Roland Eggner
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2013-02-10 3:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-01 18:22 [PATCH resend v3 0/3] kconfig: nconf: rewrite help texts, add vi-style navigation keys Roland Eggner
2013-02-01 18:27 ` [PATCH resend v3 1/3] kconfig: nconf: rewrite help texts Roland Eggner
2013-02-09 0:30 ` Yann E. MORIN
2013-02-09 3:46 ` Roland Eggner
2013-02-09 11:23 ` Yann E. MORIN
2013-02-10 3:00 ` Roland Eggner [this message]
2013-02-01 18:30 ` [PATCH resend v3 2/3] kconfig: nconf: rewrite labels of function keys line Roland Eggner
2013-02-01 18:33 ` [PATCH resend v3 3/3] kconfig: nconf: add vi-style navigation keys Roland Eggner
2013-02-09 1:03 ` Yann E. MORIN
2013-02-09 5:07 ` Roland Eggner
2013-02-09 11:36 ` Yann E. MORIN
2013-02-10 4:09 ` Roland Eggner
2013-02-03 10:16 ` [PATCH resend v3 0/3] kconfig: nconf: rewrite help texts, " yann.morin.1998
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=20130210030030.GA20308@mobil.systemanalysen.net \
--to=edvx1@systemanalysen.net \
--cc=dvv.kernel@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=sboyd@codeaurora.org \
--cc=yann.morin.1998@free.fr \
/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