From: yann.morin.1998@free.fr
To: Roland Eggner <edvx1@systemanalysen.net>
Cc: "Yann E. MORIN" <yann.morin.1998@free.fr>,
Dmitry Voytik <dvv.kernel@gmail.com>,
Michal Marek <mmarek@suse.cz>,
Stephen Boyd <sboyd@codeaurora.org>,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org
Subject: Re: [PATCH resend v3 0/3] kconfig: nconf: rewrite help texts, add vi-style navigation keys
Date: Sun, 03 Feb 2013 11:16:33 +0100 [thread overview]
Message-ID: <1359886593.510e3901cb3fa@imp.free.fr> (raw)
In-Reply-To: <20130201182237.GA11098@mobil.systemanalysen.net>
Rolland, All,
Quoting Roland Eggner <edvx1@systemanalysen.net>:
> Yann, Michal,
>
> thanks for advice and comments to v2, I tried to address all and posted v3
> a week ago. Got no reply and resent now.
I'm on the move (at FOSDEM). I will look at this when I'm
back home (wednesday).
> I would like to see this in 3.9.
> How to proceed?
Given the current state of the -rc series, I think we still
have a bit of time before the merge window opens again.
Regards,
Yann E. MORIN.
prev parent reply other threads:[~2013-02-03 10:16 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
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 ` yann.morin.1998 [this message]
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=1359886593.510e3901cb3fa@imp.free.fr \
--to=yann.morin.1998@free.fr \
--cc=dvv.kernel@gmail.com \
--cc=edvx1@systemanalysen.net \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=sboyd@codeaurora.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