From: Michal Marek <mmarek@suse.cz>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: linux-kbuild@vger.kernel.org,
Roland Eggner <edvx1@systemanalysen.net>,
Dmitry Voytik <dvv.kernel@gmail.com>
Subject: Re: [pull request] Pull request for branch yem-kconfig-for-next
Date: Wed, 20 Feb 2013 10:57:37 +0100 [thread overview]
Message-ID: <51249E11.3090808@suse.cz> (raw)
In-Reply-To: <201302191916.32691.yann.morin.1998@free.fr>
On 19.2.2013 19:16, Yann E. MORIN wrote:
> Michal, All,
>
> On Tuesday 19 February 2013 Michal Marek wrote:
>>> On Saturday 09 February 2013 Yann E. MORIN wrote:
>>>> This series by Roland, updates the help texts for the nconf frontends, and
>>>> brings it from its lingering state to (to my knowledge) an up-to-date and
>>>> complete coverage of nconf.
>> Pulled now, sorry for the delay.
>
> No problem, thank you!
>
> Shall I continue gathering kconfig changes there for you to pull?
It definitely helps me, so I appreciate if you continue doing this!
Michal
next prev parent reply other threads:[~2013-02-20 9:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-09 0:58 [pull request] Pull request for branch yem-kconfig-for-next Yann E. MORIN
2013-02-09 0:58 ` [PATCH 1/2] kconfig: nconf: rewrite help texts Yann E. MORIN
2013-02-09 0:58 ` [PATCH 2/2] kconfig: nconf: rewrite labels of function keys line Yann E. MORIN
2013-02-16 11:18 ` [pull request] Pull request for branch yem-kconfig-for-next Yann E. MORIN
2013-02-19 12:43 ` Michal Marek
2013-02-19 18:16 ` Yann E. MORIN
2013-02-20 9:57 ` Michal Marek [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-06-29 14:21 Yann E. MORIN
2013-06-18 22:44 Yann E. MORIN
2013-06-19 20:40 ` Michal Marek
2013-06-19 21:01 ` Yann E. MORIN
2013-04-29 17:59 Yann E. MORIN
2013-05-02 8:48 ` Michal Marek
2013-04-26 22:17 Yann E. MORIN
2013-04-29 12:09 ` Michal Marek
2013-04-22 21:31 Yann E. MORIN
2013-04-23 7:07 ` Yann E. MORIN
2013-01-15 23:12 Yann E. MORIN
2013-01-24 10:44 ` Michal Marek
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=51249E11.3090808@suse.cz \
--to=mmarek@suse.cz \
--cc=dvv.kernel@gmail.com \
--cc=edvx1@systemanalysen.net \
--cc=linux-kbuild@vger.kernel.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 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.