From: Thomas De Schampheleire <patrickdepinguin@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0 of 2] kconfig-package: add documentation
Date: Thu, 24 Jul 2014 20:57:52 +0200 [thread overview]
Message-ID: <patchbomb.1406228272@localhost> (raw)
This small series accompanies the previously sent series introducing a
kconfig-package infrastructure. It provides documentation both as comments
in the pkg-kconfig.mk file, and in the manual.
Depending on the feedback received on the previous series, this
documentation may need revising.
At the moment of a resend, I will merge two series in one.
Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
---
docs/manual/adding-packages-kconfig.txt | 54 +++++++++++++++++++++++++++
docs/manual/adding-packages.txt | 2 +
package/pkg-kconfig.mk | 48 ++++++++++++++++++++++++++-
3 files changed, 103 insertions(+), 1 deletions(-)
next reply other threads:[~2014-07-24 18:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-24 18:57 Thomas De Schampheleire [this message]
2014-07-24 18:57 ` [Buildroot] [PATCH 1 of 2] kconfig-package: add some comments to pkg-kconfig.mk Thomas De Schampheleire
2014-07-24 18:57 ` [Buildroot] [PATCH 2 of 2] kconfig-package: add documentation to manual Thomas De Schampheleire
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=patchbomb.1406228272@localhost \
--to=patrickdepinguin@gmail.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