From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC 0/8] Add a per-package help text
Date: Mon, 2 Feb 2015 10:30:58 +0100 [thread overview]
Message-ID: <20150202093058.GE4918@free.fr> (raw)
In-Reply-To: <1422394913-13257-1-git-send-email-thomas.petazzoni@free-electrons.com>
Thomas, All,
On 2015-01-27 22:41 +0100, Thomas Petazzoni spake thusly:
> This commit implements one item of our TODO-list, which I believe we
> added at the latest Buildroot meeting: adding a per-package help text
> to document the available make targets for this package.
While reviewing this series, I was wodering if we could also get rid of
the defconfig list in hte main help output, because it moves the real
useful help way out of the terminal.
Instead, add a new target, like "make listdefconfig" that woudl print
this big list, and document that alongside the existing *defconfig
targets.
Thoughts?
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2015-02-02 9:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-27 21:41 [Buildroot] [RFC 0/8] Add a per-package help text Thomas Petazzoni
2015-01-27 21:41 ` [Buildroot] [RFC 1/8] package: core support for " Thomas Petazzoni
2015-02-02 9:05 ` Yann E. MORIN
2015-01-27 21:41 ` [Buildroot] [RFC 2/8] pkg-kconfig: extend per-package help text with kconfig targets Thomas Petazzoni
2015-02-02 9:11 ` Yann E. MORIN
2015-01-27 21:41 ` [Buildroot] [RFC 3/8] linux: add custom per-package help text contents Thomas Petazzoni
2015-02-02 9:16 ` Yann E. MORIN
2015-01-27 21:41 ` [Buildroot] [RFC 4/8] barebox: add custom help entries Thomas Petazzoni
2015-02-02 9:20 ` Yann E. MORIN
2015-01-27 21:41 ` [Buildroot] [RFC 5/8] ccache: " Thomas Petazzoni
2015-01-28 5:51 ` Baruch Siach
2015-01-28 8:10 ` Thomas Petazzoni
2015-01-27 21:41 ` [Buildroot] [RFC 6/8] Makefile: remove uclibc, barebox, linux, busybox specific help Thomas Petazzoni
2015-02-02 9:31 ` Yann E. MORIN
2015-01-27 21:41 ` [Buildroot] [RFC 7/8] Makefile: point users to the per-package help text Thomas Petazzoni
2015-02-02 9:35 ` Yann E. MORIN
2015-01-27 21:41 ` [Buildroot] [RFC 8/8] docs/manual: update manual about <pkg>-help tagret Thomas Petazzoni
2015-02-02 9:56 ` Yann E. MORIN
2015-02-02 9:30 ` Yann E. MORIN [this message]
2015-02-02 10:37 ` [Buildroot] [RFC 0/8] Add a per-package help text 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=20150202093058.GE4918@free.fr \
--to=yann.morin.1998@free.fr \
--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