All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] help: relocate help messages specific to one package
Date: Sun, 29 Nov 2015 21:39:39 +0100	[thread overview]
Message-ID: <565B628B.2040107@mind.be> (raw)
In-Reply-To: <20151118154912.408690e7@free-electrons.com>

On 18-11-15 15:49, Thomas Petazzoni wrote:
> Hello,
> 
> On Wed, 18 Nov 2015 15:37:01 +0100, J?r?me Pouiller wrote:
>> Use $LOCAL_HELP feature in order to integrate help messages specific
>> to one package (linux-menuconfig, etc...) package they are
>> related.
>>
>> It would be possible to do it using kconfig framework, but I was not
>> sure it is necessary to document kconfig targets systematicaly.
>>
>> Signed-off-by: J?r?me Pouiller <jezz@sysmic.org>
>> ---
>>  Makefile                   | 16 ----------------
>>  boot/barebox/barebox.mk    |  5 +++++
>>  linux/linux.mk             |  7 +++++++
>>  package/busybox/busybox.mk |  4 ++++
>>  package/uclibc/uclibc.mk   |  4 ++++
>>  5 files changed, 20 insertions(+), 16 deletions(-)
> 
> I already proposed something achieving a similar thing (but more
> integrated into the package infrastructure) a while ago, and it wasn't
> accepted.
> 
> See:
> 
>   http://lists.busybox.net/pipermail/buildroot/2015-January/118159.html

 Your proposal had a lot more impact. J?r?me's proposal is diffstat-neutral
(except for 4 added empty lines, and with 5 additional lines needed in the infra
in patch 1/2). So I'm not opposed to this proposal at all.


 Regards,
 Arnout

> 
> Best regards,
> 
> Thomas
> 


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF

  parent reply	other threads:[~2015-11-29 20:39 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-18 14:37 [Buildroot] [PATCH 1/2] help: add a way to document targets declared in local.mk/external.mk Jérôme Pouiller
2015-11-18 14:37 ` [Buildroot] [PATCH 2/2] help: relocate help messages specific to one package Jérôme Pouiller
2015-11-18 14:49   ` Thomas Petazzoni
2015-11-19 10:44     ` Jérôme Pouiller
2015-11-29 20:39     ` Arnout Vandecappelle [this message]
2016-03-08 20:58   ` Arnout Vandecappelle
2015-11-29 20:26 ` [Buildroot] [PATCH 1/2] help: add a way to document targets declared in local.mk/external.mk Yann E. MORIN
2015-11-30 12:04   ` Jérôme Pouiller
2015-11-30 22:22     ` Arnout Vandecappelle
2016-03-08 20:54 ` Arnout Vandecappelle
2016-03-08 21:02   ` Thomas Petazzoni
2016-03-08 21:19     ` Thomas Petazzoni
2016-03-08 21:21     ` Arnout Vandecappelle

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=565B628B.2040107@mind.be \
    --to=arnout@mind.be \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.