From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] core/help: fix custom help without a .config
Date: Sat, 16 Apr 2016 23:07:55 +0200 [thread overview]
Message-ID: <20160416210755.GB3417@free.fr> (raw)
In-Reply-To: <20160416092808.18012cf9@free-electrons.com>
Thomas, Peter, All,
On 2016-04-16 09:28 +0200, Thomas Petazzoni spake thusly:
> On Sat, 16 Apr 2016 00:16:06 +0200, Peter Korsgaard wrote:
> > > Without this custom help thing, it is already possible to define some
> > > custom make target in external.mk that will display some help. It won't
> > > be available until a configuration is defined, but oh well, who reads
> > > help texts anyway?
> >
> > Yeah, I also think this adds too much complexity just for a pointer to
> > help text. I think we should drop it.
>
> So will you revert it?
I'll send the patches to revert it.
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:[~2016-04-16 21:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-20 21:24 [Buildroot] [PATCH] core/help: fix custom help without a .config Yann E. MORIN
2016-03-22 22:40 ` Arnout Vandecappelle
2016-03-22 22:52 ` Thomas Petazzoni
2016-04-15 22:16 ` Peter Korsgaard
2016-04-16 7:28 ` Thomas Petazzoni
2016-04-16 21:07 ` Yann E. MORIN [this message]
2016-04-17 22:51 ` Arnout Vandecappelle
2016-04-18 20:27 ` 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=20160416210755.GB3417@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