From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [pull request for next] Pull request for branch yem/kconfig
Date: Thu, 14 Nov 2013 13:45:16 +0100 [thread overview]
Message-ID: <87habf17ab.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <cover.1384386575.git.yann.morin.1998@free.fr> (Yann E. MORIN's message of "Thu, 14 Nov 2013 00:53:32 +0100")
>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:
> From: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Hello All!
> While I was at it to fix the kconfig space-can't-deselect issue, I
> decided to go a bit further, and update and clean up our kconfig.
> So here is this series for 'next'.
> Note that we ditch two of our patches: one because it is useless
> (C++-style comments), one because it's been upstreamed (probability).
> Also, the README was updated to also include copying of .gitignore,
> which was missing so far.
Committed to next, thanks. I will cherry pick patch 1 to master in a day
or two as well if no problems are noticed.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2013-11-14 12:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 23:53 [Buildroot] [pull request for next] Pull request for branch yem/kconfig Yann E. MORIN
2013-11-13 23:53 ` [Buildroot] [PATCH 1/4] support/kconfig: fix 'space' to (de)select options Yann E. MORIN
2013-11-13 23:53 ` [Buildroot] [PATCH 2/4] support/kconfig: update our README Yann E. MORIN
2013-11-13 23:53 ` [Buildroot] [PATCH 3/4] support/kconfig: remove useless patch Yann E. MORIN
2013-11-13 23:53 ` [Buildroot] [PATCH 4/4] support/kconfig: bump to kconfig from linux-3.12 Yann E. MORIN
2013-11-14 11:41 ` Peter Korsgaard
2013-11-14 12:31 ` Thomas Petazzoni
2013-11-14 17:36 ` Yann E. MORIN
2013-11-14 12:45 ` Peter Korsgaard [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=87habf17ab.fsf@dell.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/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