From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/5 v4] Introduction of kconfig-package (branch yem/patrickdp/kconfig-pkg)
Date: Mon, 4 Aug 2014 10:00:01 +0200 [thread overview]
Message-ID: <20140804100001.2e2de513@free-electrons.com> (raw)
In-Reply-To: <cover.1407079864.git.yann.morin.1998@free.fr>
Yann, Thomas,
On Sun, 3 Aug 2014 17:32:39 +0200, Yann E. MORIN wrote:
> Thomas De Schampheleire (5):
> uclibc: fixup config before calling menuconfig
> infra: introduce a kconfig-package infrastructure
> manual: add documentation for kconfig-package
> uclibc: convert to kconfig-package infrastructure
> busybox: convert to kconfig-package infrastructure
Thanks, I've applied the branch. Thanks both for working on this. It is
clearly reassuring when the branch has been in the hands of two
different developers, as it is a good indication that there has been
some independent testing from two separate persons.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-08-04 8:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-03 15:32 [Buildroot] [PATCH 0/5 v4] Introduction of kconfig-package (branch yem/patrickdp/kconfig-pkg) Yann E. MORIN
2014-08-03 15:32 ` [Buildroot] [PATCH 1/5 v4] uclibc: fixup config before calling menuconfig Yann E. MORIN
2014-08-03 15:32 ` [Buildroot] [PATCH 2/5 v4] infra: introduce a kconfig-package infrastructure Yann E. MORIN
2014-08-03 15:32 ` [Buildroot] [PATCH 3/5 v4] manual: add documentation for kconfig-package Yann E. MORIN
2014-08-03 15:32 ` [Buildroot] [PATCH 4/5 v4] uclibc: convert to kconfig-package infrastructure Yann E. MORIN
2014-08-03 15:32 ` [Buildroot] [PATCH 5/5 v4] busybox: " Yann E. MORIN
2014-08-04 8:01 ` Thomas Petazzoni
2014-08-04 8:00 ` Thomas Petazzoni [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=20140804100001.2e2de513@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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