From: "Yann E. MORIN" <yann.morin.1998@free.fr>
To: Michal Marek <mmarek@suse.cz>
Cc: Jean Delvare <jdelvare@suse.de>,
linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [pull request] Pull request for branch yem-kconfig-rc-fixes
Date: Tue, 23 Jul 2013 15:54:59 +0200 [thread overview]
Message-ID: <201307231555.00241.yann.morin.1998@free.fr> (raw)
In-Reply-To: <51EE8721.10500@suse.cz>
Michal, All,
On Tuesday 23 July 2013 15:37:37 Michal Marek wrote:
> On 17.7.2013 11:59, Jean Delvare wrote:
> > Le Tuesday 16 July 2013 à 22:39 +0200, Yann E. MORIN a écrit :
> >> From: "Yann E. MORIN" <yann.morin.1998@free.fr>
> >>
> >> Hello Michal,
> >>
> >> Please pull these post-rc1 kconfig cleanups, all after
> >> review and comments by Jean:
> >> - simplify and cleanup the symbol-search code
> >> - better documentation about the symbols ordering in search results
> >> - eye-candy in the title of the search-box in [mn]conf
> >>
> >> Regards,
> >> Yann E. MORIN.
> >
> > It looks very good to me now, thanks Yann for the good work!
>
> It does look good indeed. But I am wondering if it's necessary for 3.11.
> AFAICS the only user-visible changes are
>
> [PATCH 1/6] Documentation/kconfig: more concise and straightforward
> search explanation
> [PATCH 3/6] kconfig/[mn]conf: shorten title in search-box
>
> and the rest are code cleanups (however worthwhile), is that correct?
> There is no change in the search behavior, is there? Then I would say
> merge this for 3.12-rc1. Maybe merge the documentation patch for 3.11.
I think you can merge all for 3.12-rc1, in fact.
Even patches 1 and 3 are only eye-candy, and can well wait for 3.12.
Not sure why I wanted them in an -rc in the first place, so I'm fine
with all 6 patches going in for 3.12.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +0/33 662376056 | Software Designer | \ / CAMPAIGN | ^ |
| --==< O_o >==-- '------------.-------: X AGAINST | /e\ There is no |
| http://ymorin.is-a-geek.org/ | (*_*) | / \ HTML MAIL | """ conspiracy. |
'------------------------------'-------'------------------'--------------------'
next prev parent reply other threads:[~2013-07-23 13:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-16 20:39 Yann E. MORIN
2013-07-16 20:39 ` [PATCH 1/6] Documentation/kconfig: more concise and straightforward search explanation Yann E. MORIN
2013-07-16 20:39 ` [PATCH 2/6] kconfig: avoid multiple calls to strlen Yann E. MORIN
2013-07-16 20:39 ` [PATCH 3/6] kconfig/[mn]conf: shorten title in search-box Yann E. MORIN
2013-07-17 9:55 ` Jean Delvare
2013-07-16 20:40 ` [PATCH 4/6] kconfig: minor style fixes in symbol-search code Yann E. MORIN
2013-07-16 20:40 ` [PATCH 5/6] kconfig: don't allocate n+1 elements in temporary array Yann E. MORIN
2013-07-16 20:40 ` [PATCH 6/6] kconfig: simplify symbol-search code Yann E. MORIN
2013-07-17 9:59 ` [pull request] Pull request for branch yem-kconfig-rc-fixes Jean Delvare
2013-07-23 13:37 ` Michal Marek
2013-07-23 13:54 ` Yann E. MORIN [this message]
2013-07-23 14:36 ` Michal Marek
-- strict thread matches above, loose matches on Subject: below --
2013-05-20 15:48 Yann E. MORIN
2013-05-29 21:50 ` Yann E. MORIN
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=201307231555.00241.yann.morin.1998@free.fr \
--to=yann.morin.1998@free.fr \
--cc=jdelvare@suse.de \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
/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
all inboxes | Powered by JetHome®